Re: Porblems with Lycos.com host lookup.

From: Mark Andrews <marka@xxxxxxx>
Date: Sat, 22 Aug 2009 13:52:15 +1000

In message <65afb5970908210654s56231ce1g461a251fe9afa869@xxxxxxxxxxxxxx>, Matt
writes:

Hi all,

We are seeing odd behaviour when attempting to look up the following url
from a range of Redhat servers.

The lycos.com servers are returning malformed responses. The NS
RRset should not be for lycosmail.lycos.com. See RFC 1034 and RFC
2308. This response is wrong whether you are following RFC 1034
or RFC 1034 as modified by RFC 2308.

bigmail1.lycosmail.lycos.com. 3600 IN CNAME mail-bigmail1.bo3.lycos.com.
lycosmail.lycos.com. 3600 IN NS ns1.lycos.com.
lycosmail.lycos.com. 3600 IN NS ns2.lycos.com.
lycosmail.lycos.com. 3600 IN NS ns3.lycos.com.
lycosmail.lycos.com. 3600 IN NS ns4.lycos.com.
;; Received 214 bytes from 209.202.248.141#53(ns1.lycos.com) in 266 ms

Since lycosmail.lycos.com, bo3.lycos.com and lycos.com all have the
same servers this should have been the following for the A query
(the NS RRset is optional).

bigmail1.lycosmail.lycos.com. 3600 IN CNAME mail-bigmail1.bo3.lycos.com.
mail-bigmail1.bo3.lycos.com. 3332 IN A 209.202.248.251
bo3.lycos.com. 3600 IN NS ns1.lycos.com.
bo3.lycos.com. 3600 IN NS ns2.lycos.com.
bo3.lycos.com. 3600 IN NS ns3.lycos.com.
bo3.lycos.com. 3600 IN NS ns4.lycos.com.

and the following for the MX and AAAA queries (the NS and SOA RRsets
are optional and you can't have the NS RRset without the SOA RRset).

bigmail1.lycosmail.lycos.com. 3600 IN CNAME mail-bigmail1.bo3.lycos.com.
bo3.lycos.com. 2560 IN SOA invisible.lycos.com. nic-tech.lycos-inc.com. 1250271200 16384 2048 1048576 2560
bo3.lycos.com. 3600 IN NS ns1.lycos.com.
bo3.lycos.com. 3600 IN NS ns2.lycos.com.
bo3.lycos.com. 3600 IN NS ns3.lycos.com.
bo3.lycos.com. 3600 IN NS ns4.lycos.com.

If they weren't being served by the same servers then a referral
to the bo3.lycos.com zone should have been returned RFC 1034.

bigmail1.lycosmail.lycos.com should resolve to 209.202.248.251 but we see
the following.

[xx@xxxx ~]$ host bigmail1.lycosmail.lycos.com

Host bigmail1.lycosmail.lycos.com not found: 2(SERVFAIL)

But then if we

[xx@xxxx~]$ dig -t any bigmail1.lycosmail.lycos.com

ANY queries don't follow CNAMEs.

; <<>> DiG 9.3.4-P1 <<>> -t any bigmail1.lycosmail.lycos.com

;; global options: printcmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63245

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

;; QUESTION SECTION:

;bigmail1.lycosmail.lycos.com. IN ANY

;; ANSWER SECTION:

bigmail1.lycosmail.lycos.com. 3600 IN CNAME mail-bigmail1.bo3.lycos.com=
.

;; AUTHORITY SECTION:

lycosmail.lycos.com. 3600 IN NS ns1.lycos.com.

lycosmail.lycos.com. 3600 IN NS ns2.lycos.com.

lycosmail.lycos.com. 3600 IN NS ns3.lycos.com.

lycosmail.lycos.com. 3600 IN NS ns4.lycos.com.

;; ADDITIONAL SECTION:

ns4.lycos.com. 73682 IN A 209.202.244.142

;; Query time: 110 msec

;; SERVER: 127.0.0.1#53(127.0.0.1)

;; WHEN: Fri Aug 21 14:26:47 2009

;; MSG SIZE rcvd: 166

And then

[xx@xxxx~]$ host bigmail1.lycosmail.lycos.com

bigmail1.lycosmail.lycos.com is an alias for mail-bigmail1.bo3.lycos.com.

mail-bigmail1.bo3.lycos.com has address 209.202.248.251

Because names has cached the CNAME as the result of the ANY
query.

errors we see in the bind log

05-Aug-2009 12:53:36.118 resolver: debug 1: createfetch:
bigmail1.lycosmail.lycos.com A

05-Aug-2009 12:53:36.202 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.244.142#53

05-Aug-2009 12:53:36.286 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.248.142#53

05-Aug-2009 12:53:36.369 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.244.141#53

05-Aug-2009 12:53:36.453 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.248.141#53

05-Aug-2009 12:53:36.453 resolver: debug 1: createfetch:
bigmail1.lycosmail.lycos.com A

05-Aug-2009 12:53:36.537 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.244.141#53

05-Aug-2009 12:53:36.621 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.248.142#53

05-Aug-2009 12:53:36.704 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.244.142#53

05-Aug-2009 12:53:36.788 lame-servers: info: FORMERR resolving
'bigmail1.lycosmail.lycos.com/A/IN': 209.202.248.141#53

05-Aug-2009 12:57:31.142 resolver: debug 1: createfetch: scansafe.com A

The expected subdomain is returned, the only other FORMERR cases I=92ve see=
n
(on google) show the authority section not matching the answer.

A debug trace may be found at
http://the.earth.li/~huggie/lycos-bind9-issue.txt<http://the.earth.li/%7Ehu=
ggie/lycos-bind9-issue.txt>
Any suggestions as to what the issue is or how it may be resolved would b=
e
very welcome.

Kind Regards

Matt

--001485f79224cc3a450471a7360f
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><m=
eta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" cont=
ent=3D"Microsoft Word 11"><meta name=3D"Originator" content=3D"Microsoft Wo=
rd 11"><link rel=3D"File-List" href=3D"file:///C:%5CDOCUME%7E1%5Cmbird%5CLO=
CALS%7E1%5CTemp%5Cmsohtml1%5C03%5Cclip_filelist.xml"><style>

</style>









bigmail1.lycosmail.lycos.c=

om</a>=A0 should resolve to 209.202.248.251 but we =
see
the following.





bigmail1.lycosmail=
.lycos.com</a>

bigmail1.lycosmail.lycos.co=
m</a> not found: 2(SERVFAIL)

=A0





bigmail1.lycosma=
il.lycos.com</a>



> DiG 9.3.4-P1 <<>> -t any <a href=3D"http://big=
mail1.lycosmail.lycos.com">bigmail1.lycosmail.lycos.com</a>

=A0 printcmd



>HEADER<<- opcode: QUERY, status: NOERROR, id: 63245</=
p>







bigmail1.lycosmail.lycos.=

com</a>.=A0 IN=A0=A0=A0=A0=A0
ANY





bigmail1.lycosmail.lycos.c=

om</a>.
3600 IN=A0=A0 CNAME=A0=A0 <=
a href=3D"http://mail-bigmail1.bo3.lycos.com";>mail-bigmail1.bo3.lycos.com</=
a>.





lycosmail.lycos.com</a>.=A0=A0=A0 3600=A0=A0=A0
IN=A0=A0=A0=A0=A0 NS=A0=A0=
=A0=A0=A0 <a href=3D"http://ns1.lycos.com";>ns1.lycos.com</a>.=


lycosmail.lycos.com</a>.=A0=A0=A0 3600=A0=A0=A0
IN=A0=A0=A0=A0=A0 NS=A0=A0=
=A0=A0=A0 <a href=3D"http://ns2.lycos.com";>ns2.lycos.com</a>.=


lycosmail.lycos.com</a>.=A0=A0=A0 3600=A0=A0=A0
IN=A0=A0=A0=A0=A0 NS=A0=A0=
=A0=A0=A0 <a href=3D"http://ns3.lycos.com";>ns3.lycos.com</a>.=


lycosmail.lycos.com</a>.=A0=A0=A0 3600=A0=A0=A0
IN=A0=A0=A0=A0=A0 NS=A0=A0=
=A0=A0=A0 <a href=3D"http://ns4.lycos.com";>ns4.lycos.com</a>.=






ns4.lycos.com</a>.=A0=A0=

=A0=A0=A0=A0=A0=A0=A0 73682=A0=A0 IN=A0=A0=A0=A0=A0
A=A0=A0=A0=A0=A0=A0 209.202.244.142</=
p>









=A0 rcvd: 166







bigmail1.lycosmail.lyc=
os.com</a>

bigmail1.lycosmail.lycos.c=

om</a>
is an alias for <a href=3D"http://mail-bigmail1.bo3.lycos.com";>mail-bigmail=
1.bo3.lycos.com</a>.

mail-bigmail1.bo3.lycos.com=

</a>
has address 209.202.248.251



errors we see in th=
e bind
log

<pre>05-Aug-2009 12:53:36.118 resolver:=
debug 1: createfetch: <a href=3D"http://bigmail1.lycosmail.lycos.com";>bigm=
ail1.lycosmail.lycos.com</a> A</pre><pre>05-Aug-2009 12:53:36.202 lame-servers: info: FORMERR resolving &#3=
9;<a href=3D"http://bigmail1.lycosmail.lycos.com/A/IN";>bigmail1.lycosmail.l=
ycos.com/A/IN</a>': 209.202.244.142#53</pre>
<pre>05-Aug-2009 12:53:36.286 lame-serv=
ers: info: FORMERR resolving '<a href=3D"http://bigmail1.lycosmail.lyco=
s.com/A/IN">bigmail1.lycosmail.lycos.com/A/IN</a>': 209.202.248.142#53<=
/span></pre>
<pre>05-Aug-2009 12:53:36.369 lame-serv=
ers: info: FORMERR resolving '<a href=3D"http://bigmail1.lycosmail.lyco=
s.com/A/IN">bigmail1.lycosmail.lycos.com/A/IN</a>': 209.202.244.141#53<=
/span></pre>
<pre>05-Aug-2009 12:53:36.453 lame-serv=
ers: info: FORMERR resolving '<a href=3D"http://bigmail1.lycosmail.lyco=
s.com/A/IN">bigmail1.lycosmail.lycos.com/A/IN</a>': 209.202.248.141#53<=
/span></pre>
<pre>05-Aug-2009 12:53:36.453 resolver:=
debug 1: createfetch: <a href=3D"http://bigmail1.lycosmail.lycos.com";>bigm=
ail1.lycosmail.lycos.com</a> A</pre><pre>05-Aug-2009 12:53:36.537 lame-servers: info: FORMERR resolving &#3=
9;<a href=3D"http://bigmail1.lycosmail.lycos.com/A/IN";>bigmail1.lycosmail.l=
ycos.com/A/IN</a>': 209.202.244.141#53</pre>
<pre>05-Aug-2009 12:53:36.621 lame-serv=
ers: info: FORMERR resolving '<a href=3D"http://bigmail1.lycosmail.lyco=
s.com/A/IN">bigmail1.lycosmail.lycos.com/A/IN</a>': 209.202.248.142#53<=
/span></pre>
<pre>05-Aug-2009 12:53:36.704 lame-serv=
ers: info: FORMERR resolving '<a href=3D"http://bigmail1.lycosmail.lyco=
s.com/A/IN">bigmail1.lycosmail.lycos.com/A/IN</a>': 209.202.244.142#53<=
/span></pre>
<pre>05-Aug-2009 12:53:36.788 lame-serv=
ers: info: FORMERR resolving '<a href=3D"http://bigmail1.lycosmail.lyco=
s.com/A/IN">bigmail1.lycosmail.lycos.com/A/IN</a>': 209.202.248.141#53<=
/span></pre>
<pre>05-Aug-2009 12:57:31.142 resolver:=
debug 1: createfetch: <a href=3D"http://scansafe.com";>scansafe.com</a> A</=
span></pre><pre>=A0</pre>

=A0the authority section not matching the ans=
wer.



http://the.earth.li/~huggie/lycos-bind9-issue.txt</a>
=A0=A0Any suggestions as to what the issue is
or how it may be resolved would be very welcome.





 Mat=
t 

--001485f79224cc3a450471a7360f--

--===============8305037449375662968==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
bind-users mailing list
bind-users@xxxxxxxxxxxxx
https://lists.isc.org/mailman/listinfo/bind-users
--===============8305037449375662968==--

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@xxxxxxx
.

Prev by Date: Re: Format of 'dig -k' "TSIG key file"?
Next by Date: Re: Porblems with Lycos.com host lookup.
Previous by thread: Porblems with Lycos.com host lookup.
Next by thread: Re: Porblems with Lycos.com host lookup.
Index(es):
- Date
- Thread

Relevant Pages

Re: Porblems with Lycos.com host lookup.
... See RFC 1034 and RFC ... 3600 IN CNAME mail-bigmail1.bo3.lycos.com. ... Host bigmail1.lycosmail.lycos.com not found: 2 ... ers: info: FORMERR resolving 'http://bigmail1.lycosmail.lyco= ...
(comp.protocols.dns.bind)
Re: 550 5.7.1 NDR caused by Exchange using A record instead of MX
... Thanks for the RFC reference David. ... If that initial mx query ... Mail servers are so touchy anymore because of SPAM that servers ... > Exchange is required to query the A record if no MX records exist. ...
(microsoft.public.exchange.connectivity)
Re: Email / Echange problem. Cant rec. emails
... I just got off the phone with godaddy. ... Mail: FAIL - Connect to mail servers ERROR: I could not find any ... Most SMTP servers will retry for a few days - but you could have someone do ... I did not create any CNAME for sure. ...
(microsoft.public.windows.server.sbs)
Re: google.com get redirected to google.co.uk
... When you say you are still being redirected, do you mean that when you query ... CNAME to www.google.co.uk? ... them that this is a problem on their servers - not yours. ... If you provide the IP address of your ISP's DNS servers, ...
(microsoft.public.windows.server.dns)
Re: Can not resolve ecx.images-amazon.com.
... Am I creating a secondary or Primary zone, also any idea why my DNS server is ... not picking this info up from the root servers? ... servers, just have no clue why it is not. ... is a CNAME that points to another CNAME, ...
(microsoft.public.windows.server.dns)