Andrew,
Check your email. I wrote a tiny program to perform the DNS request and display any errors.
New install - no AI filters
Re: New install - no AI filters
Hi @RandyW,
Also following this thread.
Very similar results... also in Australia, also using IPv6
C:\Windows\System32>nslookup rmnoise1.rmnoise.com
Server: dns.google
Address: 2001:4860:4860::8888
Non-authoritative answer:
Name: rmnoise1.ournetplace.com
Address: 184.80.221.105
Aliases: rmnoise1.rmnoise.com
If it is OK, I'd prefer not to run a random .exe if you can just give me the commands of what you would like to test I'm pretty handy with most things technology.
Also following this thread.
Very similar results... also in Australia, also using IPv6
C:\Windows\System32>nslookup rmnoise1.rmnoise.com
Server: dns.google
Address: 2001:4860:4860::8888
Non-authoritative answer:
Name: rmnoise1.ournetplace.com
Address: 184.80.221.105
Aliases: rmnoise1.rmnoise.com
If it is OK, I'd prefer not to run a random .exe if you can just give me the commands of what you would like to test I'm pretty handy with most things technology.
Re: New install - no AI filters
Here is the output from that program from VK2ASG:
C:\Users\TOSHIBA L850>"C:\Users\TOSHIBA L850\Downloads\dnstester.exe
error: All nameservers failed to answer the query servers.rmnoise.com. IN TXT: Server Do53:192.168.0.1@53 answered A DNS query response does not respond to the question asked.
internet: server launcher: warning: could not get DNS
I looked at the code from the resolver library. That error appears to be when the DNS server responds with something that wasn't asked. For example, before we asked for "servers.rmnoise.com" but the reply was for "servers.rmnoise.com.modem"
I would like to see the list of DNS servers. Run the following from the command line:
ipconfig /all
(If you want, just copy/paste the sections for "DNS servers". There may be more than one section.)
Also try this from the command line:
nslookup -type=txt servers.rmnoise.com 192.168.0.1
C:\Users\TOSHIBA L850>"C:\Users\TOSHIBA L850\Downloads\dnstester.exe
error: All nameservers failed to answer the query servers.rmnoise.com. IN TXT: Server Do53:192.168.0.1@53 answered A DNS query response does not respond to the question asked.
internet: server launcher: warning: could not get DNS
I looked at the code from the resolver library. That error appears to be when the DNS server responds with something that wasn't asked. For example, before we asked for "servers.rmnoise.com" but the reply was for "servers.rmnoise.com.modem"
I would like to see the list of DNS servers. Run the following from the command line:
ipconfig /all
(If you want, just copy/paste the sections for "DNS servers". There may be more than one section.)
Also try this from the command line:
nslookup -type=txt servers.rmnoise.com 192.168.0.1
Re: New install - no AI filters
We solved VK3DMA's DNS problem (via email), and that problem appears to be unrelated to yours.
While troubleshooting, I learned more about how the resolver library works. Please check your email. I sent you another diagnostic program to try.
While troubleshooting, I learned more about how the resolver library works. Please check your email. I sent you another diagnostic program to try.
Re: New install - no AI filters
Status update: A workaround was necessary.
a) If available, Windows uses IPv6 DNS which explains why everything else seems to work
b) RM Noise includes its own resolution library which uses IPv4 DNS by default
c) VK2ASG's router was providing the DNS server 192.168.0.1 via DHCP
d) 192.168.0.1 always responds with erroneous data, regardless if querying RM Noise names or any other name
e) 192.168.0.1 appears to be the router, and it intercepts ALL DNS requests, such as queries to 8.8.8.8, so DNS could not be manually configured
Because of (b) through (e) the only workaround was to directly provide RM Noise with the server IP numbers. This workaround was successful.
a) If available, Windows uses IPv6 DNS which explains why everything else seems to work
b) RM Noise includes its own resolution library which uses IPv4 DNS by default
c) VK2ASG's router was providing the DNS server 192.168.0.1 via DHCP
d) 192.168.0.1 always responds with erroneous data, regardless if querying RM Noise names or any other name
e) 192.168.0.1 appears to be the router, and it intercepts ALL DNS requests, such as queries to 8.8.8.8, so DNS could not be manually configured
Because of (b) through (e) the only workaround was to directly provide RM Noise with the server IP numbers. This workaround was successful.