I have installed Dynamic DNS and got it working.
It does, however, appear to have broken the DNS for my home network. None of my internal hostnames are now resolving.
Any ideas how to troubleshoot this issue?
I can ping my router using port 53.
PS C:\Users\> Test-NetConnection 192.168.x.x -p 53 ComputerName : 192.168.x.x
RemoteAddress : 192.168.x.x
RemotePort : 53
InterfaceAlias : Ethernet
SourceAddress : 192.168.x.x
TcpTestSucceeded : True
I have adblock installed and that is still fully functional and my router is serving internet DNS queries to my internal devices.
What's the relations between the ddns name, and your internal host names ?
There is zero relationship.
I used a password manager to create a 20 digit random alphanumeric string for the DDNS entry.
Then the ddns shouldn't be the issue.
If you do a nslookup of some internal dns name, what's the error message?
Post the command + output.
As a guess... Try using a separate public DNS server in DDNS configuration.
If you do a nslookup of some internal dns name, what's the error message?
Post the command + output.
Server: UnKnown
Address: fd00:48ae:65f2::1
Ok, let's try it one more time ...
Post the command + output
PS C:\Users\> nslookup rp4-openwrt.homelan
Server: UnKnown
Address: fd00:48ae:65f2::1
*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for rp4-openwrt.homelan
Check if .homelan isn't by any chance on the adblock list.
I've paused adblock, but it hasn't made any difference.
Ok, and what's the dns IP announced by the DHCP ?
ipconfig /all
Btw, no need to mask 192 IPs, they're not public.
It isn't announcing a DNS server.
Then it's probably the reason why it doesn't work.
Try that nslookup command again, add the IP of your internal DNS after the domain name.
nslookup rp4-openwrt.homelan 192.168.x.y
Then you need to check why there's no dns sent out by the DHCP.
1 Like
I'm thinking that it might be because I disabled ipv6 on my home LAN and maybe that was being used for internal DNS?
I think that maybe adblock relies upon ipv6?
But I can't remember what the settings were...
I think this address is ipv6
PS C:\Users\> nslookup rp4-openwrt.homelan
Server: UnKnown
Address: fd00:48ae:65f2::1
*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for rp4-openwrt.homelan
OK, so the issue does appear to be related to ipv6.
When I enabled IPv6 DHCP server mode on my LAN interface, it kicked into life.
It was a bit odd.
Powershell returned a successful nslookup. I only performed a single test.
PS C:\Users\> nslookup rp4-openwrt.homelan
Server: rp4-openwrt.homelan
Address: 192.168.0.1
Name: rp4-openwrt.homelan
Addresses: fd94:9be3:80bd::1
192.168.0.1
So I then tried switching RA-Service and NDP-Proxy from 'relay' to 'disabled'.
Powershell then failed to resolve the FQDN, so I switched the settings back - but Powershell continued to fail.
PS C:\Users\> nslookup rp4-openwrt.homelan
Server: UnKnown
Address: fd94:9be3:80bd::1
UnKnown can't find rp4-openwrt.homelan: No response from server
But, despite that, pings to the FQDN are successful.
PS C:\Users\> ping rp4-openwrt.homelan
Pinging rp4-openwrt.homelan [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
And I am able to access my router via the FQDN.
I think the ipv6 DHCP server may have been automatically configured by Adblock?
Unfortunately, the issue isn't resolved.
When testing with my phone, I get contradictory results.
Ping = unknown host
DNS lookup = success
Browsing to the hostname on my phone results in a DNS error.
Any suggestions?
