I'm having an issue with DNS resolution of external addresses on my network.
For this example I'm using the local movie theatre's web site, as this one is consistently providing me with issues.
When I do an nslookup on my HDA I get the correct DNS info, but when I do an nslookup on a PC that uses the HDA as its DNS server I get black.amahi.org.
From the HDA:
[aaron@localhost ~]$ nslookup www.cineplex.com
Server: 192.168.1.10
Address: 192.168.1.10#53
Non-authoritative answer:
www.cineplex.com canonical name = www-cineplex-com-tls12.zenedge.net.
www-cineplex-com-tls12.zenedge.net canonical name = 104-225-137-39-tls12.zenedge.net.
Name: 104-225-137-39-tls12.zenedge.net
Address: 104.225.137.39
From a PC using the HDA as DNS:
>nslookup www.cineplex.com
Server: hda.amahi.net
Address: 192.168.1.10
Non-authoritative answer:
Name: black.amahi.org
Address: 66.165.251.198
Aliases: www.cineplex.com.amahi.net
When I try to connect to the web site from the HDA directly (using Lynx via command line) I am given a 403 Forbidden error as it directs me to 66.165.251.198, so even on the HDA locally I am experiencing this issue.
When I bypass my HDA and connect directly to my modem I am able to resolve everything without issue.
System info: https://da.gd/FGmK -> https://paste.fedoraproject.org/paste/n ... -IPMGxwbA/
CLOSED: DNS not resolving properly
CLOSED: DNS not resolving properly
Last edited by aarondyck on Fri Apr 05, 2019 3:49 pm, edited 1 time in total.
Re: DNS not resolving properly
I am marking this topic as closed.
My router was the source of the problem. It would appear that I am not the first person to experience this issue with a Netgear router. The resolution was to change the MAC Address of the router.
My router was the source of the problem. It would appear that I am not the first person to experience this issue with a Netgear router. The resolution was to change the MAC Address of the router.
Who is online
Users browsing this forum: No registered users and 7 guests