Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
named oddity
7 views
Skip to first unread message
Mike Scott
Apr 29, 2013, 4:25:45 AM4/29/13
to
I've had named running for quite some time without a hiccup on my home
machine, which also acts a mail server. It has been running as a caching
server.
Over the weekend, an email was being 451-rejected as sender domain not
resolvable, and indeed I found that 'tescofreetime.com' lookups returned
no result. OTOH, a check on the net showed the problem to be purely
local, and also not affecting any other address (at least, that I've
noticed, except pipex as noted below).
FWIW, I get:
data# dig -t any tescofreetime.com
; <<>> DiG 9.6.-ESV-R3 <<>> -t any tescofreetime.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6542
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;tescofreetime.com. IN ANY
;; Query time: 8 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 29 08:56:41 2013
;; MSG SIZE rcvd: 35
and after 'rndc dumpdb', the dump file contains just:
; glue
tescofreetime.com. 172722 NS ns0-t.dns.pipex.net.
172722 NS ns1-t.dns.pipex.net.
(embedded in lots of other stuff.)
I'm hazy about the internals, but I /think/ that means those pipex
servers are to be used for this domain -- and indeed, a dns query on
either of them fails:
; <<>> DiG 9.6.-ESV-R3 <<>> -t any ns0-t.dns.pipex.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51155
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns0-t.dns.pipex.net. IN ANY
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 29 09:08:20 2013
;; MSG SIZE rcvd: 37
This time the named dump file contains no mention of ns0-t.dns.pipex.net.
Yet an online check shows others' systems resolve the pipex address too.
I've temporarily reconfigured to forward requests to google's public
servers as a workaround. But I'd much rather a proper solution. Any
thoughts please on where to look next? Thanks.
This is with BIND 9.6.-ESV-R3 on fbsd 8.2. And the current named.root
file (Jan 3, 2013).
--
Mike Scott (unet2 <at> [deletethis] scottsonline.org.uk)
Harlow Essex England
machine, which also acts a mail server. It has been running as a caching
server.
Over the weekend, an email was being 451-rejected as sender domain not
resolvable, and indeed I found that 'tescofreetime.com' lookups returned
no result. OTOH, a check on the net showed the problem to be purely
local, and also not affecting any other address (at least, that I've
noticed, except pipex as noted below).
FWIW, I get:
data# dig -t any tescofreetime.com
; <<>> DiG 9.6.-ESV-R3 <<>> -t any tescofreetime.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6542
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;tescofreetime.com. IN ANY
;; Query time: 8 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 29 08:56:41 2013
;; MSG SIZE rcvd: 35
and after 'rndc dumpdb', the dump file contains just:
; glue
tescofreetime.com. 172722 NS ns0-t.dns.pipex.net.
172722 NS ns1-t.dns.pipex.net.
(embedded in lots of other stuff.)
I'm hazy about the internals, but I /think/ that means those pipex
servers are to be used for this domain -- and indeed, a dns query on
either of them fails:
; <<>> DiG 9.6.-ESV-R3 <<>> -t any ns0-t.dns.pipex.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51155
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns0-t.dns.pipex.net. IN ANY
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 29 09:08:20 2013
;; MSG SIZE rcvd: 37
This time the named dump file contains no mention of ns0-t.dns.pipex.net.
Yet an online check shows others' systems resolve the pipex address too.
I've temporarily reconfigured to forward requests to google's public
servers as a workaround. But I'd much rather a proper solution. Any
thoughts please on where to look next? Thanks.
This is with BIND 9.6.-ESV-R3 on fbsd 8.2. And the current named.root
file (Jan 3, 2013).
--
Mike Scott (unet2 <at> [deletethis] scottsonline.org.uk)
Harlow Essex England
Bruce Esquibel
Apr 29, 2013, 8:37:04 AM4/29/13
to
Mike Scott <usen...@scottsonline.org.uk.invalid> wrote:
> I've temporarily reconfigured to forward requests to google's public
> servers as a workaround. But I'd much rather a proper solution. Any
> thoughts please on where to look next? Thanks.
Try using dig like this:
> I've temporarily reconfigured to forward requests to google's public
> servers as a workaround. But I'd much rather a proper solution. Any
> thoughts please on where to look next? Thanks.
dig -t mx tescofreetime.com +trace
You aren't asking for the mail records with "any".
They don't seem to have any A records for that domain, but do have MX ones.
tescofreetime.com. 86298 IN MX 10 cust7123-2.in.mailcontrol.com.
tescofreetime.com. 86298 IN MX 10 cust7123-1.in.mailcontrol.com.
tescofreetime.com. 86298 IN MX 50 mailhost.tescofreetime.com.
tescofreetime.com. 86298 IN MX 90 fallback.mail.uk.uu.net.
They probably broke something that is being fixed, when I first checked
the records with them, I was getting...
WARNING: recursion requested but not available
Which usually means the servers at pipex.net didn't have any information for
them, period.
It's not your name server, just a burp on the internet.
-bruce
b...@ripco.com
Mike Scott
Apr 29, 2013, 10:41:16 AM4/29/13
to
On 29/04/13 13:37, Bruce Esquibel wrote:
> Mike Scott <usen...@scottsonline.org.uk.invalid> wrote:
>
>> I've temporarily reconfigured to forward requests to google's public
>> servers as a workaround. But I'd much rather a proper solution. Any
>> thoughts please on where to look next? Thanks.
>
>
> Try using dig like this:
>
> dig -t mx tescofreetime.com +trace
>
> You aren't asking for the mail records with "any".
Oh; I've always thought 'any' meant just that, thanks for the correction.
> Mike Scott <usen...@scottsonline.org.uk.invalid> wrote:
>
>> I've temporarily reconfigured to forward requests to google's public
>> servers as a workaround. But I'd much rather a proper solution. Any
>> thoughts please on where to look next? Thanks.
>
>
> Try using dig like this:
>
> dig -t mx tescofreetime.com +trace
>
> You aren't asking for the mail records with "any".
>
> They don't seem to have any A records for that domain, but do have MX ones.
>
> tescofreetime.com. 86298 IN MX 10 cust7123-2.in.mailcontrol.com.
> tescofreetime.com. 86298 IN MX 10 cust7123-1.in.mailcontrol.com.
> tescofreetime.com. 86298 IN MX 50 mailhost.tescofreetime.com.
> tescofreetime.com. 86298 IN MX 90 fallback.mail.uk.uu.net.
>
> They probably broke something that is being fixed, when I first checked
> the records with them, I was getting...
>
> WARNING: recursion requested but not available
>
> Which usually means the servers at pipex.net didn't have any information for
> them, period.
>
> It's not your name server, just a burp on the internet.
With that, I get
%dig -t mx tescofreetime.com +trace
; <<>> DiG 9.6.-ESV-R3 <<>> -t mx tescofreetime.com +trace
;; global options: +cmd
. 3600000 IN NS F.ROOT-SERVERS.NET.
. 3600000 IN NS J.ROOT-SERVERS.NET.
. 3600000 IN NS M.ROOT-SERVERS.NET.
. 3600000 IN NS E.ROOT-SERVERS.NET.
. 3600000 IN NS G.ROOT-SERVERS.NET.
. 3600000 IN NS L.ROOT-SERVERS.NET.
. 3600000 IN NS C.ROOT-SERVERS.NET.
. 3600000 IN NS I.ROOT-SERVERS.NET.
. 3600000 IN NS B.ROOT-SERVERS.NET.
. 3600000 IN NS H.ROOT-SERVERS.NET.
. 3600000 IN NS K.ROOT-SERVERS.NET.
. 3600000 IN NS D.ROOT-SERVERS.NET.
. 3600000 IN NS A.ROOT-SERVERS.NET.
;; Received 228 bytes from 127.0.0.1#53(127.0.0.1) in 5 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
;; Received 507 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 19 ms
tescofreetime.com. 172800 IN NS ns0-t.dns.pipex.net.
tescofreetime.com. 172800 IN NS ns1-t.dns.pipex.net.
;; Received 120 bytes from 192.55.83.30#53(m.gtld-servers.net) in 339 ms
;; connection timed out; no servers could be reached
Segmentation fault (core dumped)
%
(ooops!!)
If it really is a 'burp', it's a long one, been failing like this since
Saturday. I'll hang on and see what happens later in the week.
Thanks.
Mike Scott
Apr 30, 2013, 4:07:02 AM4/30/13
to
On 29/04/13 15:41, Mike Scott wrote:
> On 29/04/13 13:37, Bruce Esquibel wrote:
>> Mike Scott <usen...@scottsonline.org.uk.invalid> wrote:
>>
>>> I've temporarily reconfigured to forward requests to google's public
>>> servers as a workaround. But I'd much rather a proper solution. Any
>>> thoughts please on where to look next? Thanks.
Comfortingly perhaps, but unhelpfully, even google's dns servers
> On 29/04/13 13:37, Bruce Esquibel wrote:
>> Mike Scott <usen...@scottsonline.org.uk.invalid> wrote:
>>
>>> I've temporarily reconfigured to forward requests to google's public
>>> servers as a workaround. But I'd much rather a proper solution. Any
>>> thoughts please on where to look next? Thanks.
(8.8.8.8, 8.8.4.4) today fail the request. So it looks like pipex have
messed up.
Of course, I can't even email the tescofreetime.com support address. So
I've just rung them up - very helpful man on the tech admin phone line
also now sees the problem, so I guess it'll get sorted.
0 new messages