doing some testing here this morning and went to login to af6hf.ampr.org and saw the following:
debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21...
just curious what's going on here. can we now assign any ip addresses to our delegated domain namespace? I had always thought that foo.ampr.org would be placed in 44/8 ip space.
Eric AF6EP
Yes you can.
Take a look at ftp://hamradio.ucsd.edu/pub/amprhosts and you will see the occasional ampr.org pointing to a non 44 address.
But be aware that this will only work for the forward resolving part. The reverse DNS for these non 44 ips will not be an ampr.org address, but rather whatever the ISP of the IP has set.
73s Robbie ON4SAX
On Thu, Jul 31, 2014 at 8:41 PM, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ doing some testing here this morning and went to login to af6hf.ampr.org and saw the following:
debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21...
just curious what's going on here. can we now assign any ip addresses to our delegated domain namespace? I had always thought that foo.ampr.org would be placed in 44/8 ip space.
Eric AF6EP
It seems that the provider of the machine you originated the connect from offers a little "help". Instead of rejecting the DNS request (af6hf doesn't resolve), it offers a fake reply, so a browser request will be redirected to some page (usually advertisements or some search engine). In your case: Name: unallocated.barefruit.co.uk Address: 92.242.140.21
This practice becomes more and more popular among providers.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Eric Fort Sent: Thursday, July 31, 2014 21:42 To: AMPRNet working group Subject: [44net] ampr.org hostname resolves to non 44/8 ip - what's up here?
...
debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21...
...
Our ISP also did this without notifying anyone, and I contacted the ISP (eastlink), they were very helpful at tech tier 2 and gave me two other DNS servers that did not do this..installed these DNS servers in their router and the problem went away.. (told them this breaks many things on my system including ping giving false replies)..in our case it always redirected us to a search engine in California, lol On 07/31/2014 03:54 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ It seems that the provider of the machine you originated the connect from offers a little "help". Instead of rejecting the DNS request (af6hf doesn't resolve), it offers a fake reply, so a browser request will be redirected to some page (usually advertisements or some search engine). In your case: Name: unallocated.barefruit.co.uk Address: 92.242.140.21
This practice becomes more and more popular among providers.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Eric Fort Sent: Thursday, July 31, 2014 21:42 To: AMPRNet working group Subject: [44net] ampr.org hostname resolves to non 44/8 ip - what's up here?
...
debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21...
...
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
I'm aware that verizon does this as well which is the root source of the issue as marius pointed out but in my case as the hosts in question get their dns via dhcp from a router provided by the isp which for political reasons I won't go into I have no access to so as to change the resolvers it uses. thus the fix will be telling each host to ignore the resolvers it's given via dhcp and use others instead.... or just simply placing these boxen outside the dhcp range of the router and setting them up on static ip in a range not issued by the router but still within the routers private subnet.
Eric
On Thu, Jul 31, 2014 at 12:08 PM, jj ve1jot@eastlink.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ Our ISP also did this without notifying anyone, and I contacted the ISP (eastlink), they were very helpful at tech tier 2 and gave me two other DNS servers that did not do this..installed these DNS servers in their router and the problem went away.. (told them this breaks many things on my system including ping giving false replies)..in our case it always redirected us to a search engine in California, lol
On 07/31/2014 03:54 PM, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ It seems that the provider of the machine you originated the connect from offers a little "help". Instead of rejecting the DNS request (af6hf doesn't resolve), it offers a fake reply, so a browser request will be redirected to some page (usually advertisements or some search engine). In your case: Name: unallocated.barefruit.co.uk Address: 92.242.140.21
This practice becomes more and more popular among providers.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Eric Fort Sent: Thursday, July 31, 2014 21:42 To: AMPRNet working group Subject: [44net] ampr.org hostname resolves to non 44/8 ip - what's up here?
...
debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21...
...
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Ok, glad you have a way around it anyhow...it's appalling that they (ISP's) have done this...ours has an "opt-out" feature on their web page, but i'd soon discovered that my opt-out settings were reset every time the ip lease would change on the router..the motorola router has a wi-fi feature which we can pay extra to enable, and once enabling the wifi I was able to go into their router and change a few things, such as DMZ and also manually inserint DNS servers among other tweaks..so now I pay an extra $5.00/month for that..but at least I can now administer the router...GL Eric... Cheers, de John On 07/31/2014 04:18 PM, Eric Fort wrote:
(Please trim inclusions from previous messages) _______________________________________________ I'm aware that verizon does this as well which is the root source of the issue as marius pointed out but in my case as the hosts in question get their dns via dhcp from a router provided by the isp which for political reasons I won't go into I have no access to so as to change the resolvers it uses. thus the fix will be telling each host to ignore the resolvers it's given via dhcp and use others instead.... or just simply placing these boxen outside the dhcp range of the router and setting them up on static ip in a range not issued by the router but still within the routers private subnet.
Eric
Why do they do this ?
On Thu, Jul 31, 2014 at 9:40 PM, jj ve1jot@eastlink.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ Ok, glad you have a way around it anyhow...it's appalling that they (ISP's) have done this...ours has an "opt-out" feature on their web page, but i'd soon discovered that my opt-out settings were reset every time the ip lease would change on the router..the motorola router has a wi-fi feature which we can pay extra to enable, and once enabling the wifi I was able to go into their router and change a few things, such as DMZ and also manually inserint DNS servers among other tweaks..so now I pay an extra $5.00/month for that..but at least I can now administer the router...GL Eric... Cheers, de John
On 07/31/2014 04:18 PM, Eric Fort wrote:
(Please trim inclusions from previous messages) _______________________________________________ I'm aware that verizon does this as well which is the root source of the issue as marius pointed out but in my case as the hosts in question get their dns via dhcp from a router provided by the isp which for political reasons I won't go into I have no access to so as to change the resolvers it uses. thus the fix will be telling each host to ignore the resolvers it's given via dhcp and use others instead.... or just simply placing these boxen outside the dhcp range of the router and setting them up on static ip in a range not issued by the router but still within the routers private subnet.
Eric
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
because they can..... because breaking the entire dns infrastructure drives revenue. because most non-technical users don't know any better or how they'd be better off if it worked properly and failed to resolve even to the point of liking it when is sometimes asks, "did you mean.... ?"
Eric
On Thu, Jul 31, 2014 at 2:18 PM, Robbie De Lise robbie.delise@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Why do they do this ?
On Thu, Jul 31, 2014 at 9:40 PM, jj ve1jot@eastlink.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ Ok, glad you have a way around it anyhow...it's appalling that they (ISP's) have done this...ours has an "opt-out" feature on their web page, but i'd soon discovered that my opt-out settings were reset every time the ip lease would change on the router..the motorola router has a wi-fi feature which we can pay extra to enable, and once enabling the wifi I was able to go into their router and change a few things, such as DMZ and also manually inserint DNS servers among other tweaks..so now I pay an extra $5.00/month for that..but at least I can now administer the router...GL Eric... Cheers, de John
On 07/31/2014 04:18 PM, Eric Fort wrote:
(Please trim inclusions from previous messages) _______________________________________________ I'm aware that verizon does this as well which is the root source of the issue as marius pointed out but in my case as the hosts in question get their dns via dhcp from a router provided by the isp which for political reasons I won't go into I have no access to so as to change the resolvers it uses. thus the fix will be telling each host to ignore the resolvers it's given via dhcp and use others instead.... or just simply placing these boxen outside the dhcp range of the router and setting them up on static ip in a range not issued by the router but still within the routers private subnet.
Eric
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On Thu, 31 Jul 2014 12:18:28 -0700, Eric Fort eric.fort@gmail.com wrote:
or just simply placing these boxen outside the dhcp range of the router and setting them up on static ip in a range not issued by the router but still within the routers private subnet.
Do this.
On most systems, such as Windows XP or Windows 7 you can set the DNS IP's independently of the DHCP, making them higher priority than any they might get from DHCP. Once set, Windows 7 won't even insert the DHCP DNS IP's into its configuration on the interface. Fortunately, Verizon's Actiontec routers always point to themselves as the DNS and the router passes the queries to the DNS servers it has received when it logged in via PPPoE. It's these servers that are screwing with your DNS. I use DHCP to accept the LAN IP and mask but manually set my DNS on all my boxes in-house. Same principles apply to my Linux and OSX boxes.
Surprisingly, Google's servers are compliant with the standard and don't return an address for your af6hf.ampr.org which has no entry. Wow, they're not evil.
When Verizon stopped using Level3's DNS servers and they started "monetizing" me with their DNS servers, I stopped using their DNS servers. Except for this issue, I'm VERY happy with my FiOS service.
thanks marius, I shall have to fix the resolv.conf on my hosts and set them not to be modified via dhcp.
Eric AF6EP
On Thu, Jul 31, 2014 at 11:54 AM, Marius Petrescu marius@yo2loj.ro wrote:
(Please trim inclusions from previous messages) _______________________________________________ It seems that the provider of the machine you originated the connect from offers a little "help". Instead of rejecting the DNS request (af6hf doesn't resolve), it offers a fake reply, so a browser request will be redirected to some page (usually advertisements or some search engine). In your case: Name: unallocated.barefruit.co.uk Address: 92.242.140.21
This practice becomes more and more popular among providers.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Eric Fort Sent: Thursday, July 31, 2014 21:42 To: AMPRNet working group Subject: [44net] ampr.org hostname resolves to non 44/8 ip - what's up here?
...
debian@arm:~$ telnet af6hf.ampr.org Trying 92.242.140.21...
...
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Eric Fort -
Geoff Joy -
jj -
Marius Petrescu -
Robbie De Lise