31 Jul
2014
31 Jul
'14
3:18 p.m.
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(a)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(a)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(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net