Re: [9fans] wildcard dns cname

Re: [9fans] wildcard dns cname

[erik quanstrom]

> cpu% ndb/dnsdebug
> > @10.0.0.1
> > foobar
> 8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local ip
> <delay>

sure looks like your the dns packet is being dropped.
you might want to check your routing.  can you ping 10.0.0.1
from your linux host (with the interfaces dns is allowed to talk on).
make sure you see those icmp packets on your plan 9 system
before proceeding.

- erik

Re: [9fans] wildcard dns cname

[slash]

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

Yes ping works and I can also make nslookups for hosts that don't match the
wildcard.

$ nslookup server.local
Server: 10.0.0.1
Address: 10.0.0.1#53

Name: server.local
Address: 10.0.0.1

$ nslookup other.local
Server: 10.0.0.1
Address: 10.0.0.1#53

Name: other.local
Address: 10.0.0.2

snoopy confirms that my server sees the expected packets on the right
interface.

Where is the problem?


On Sun, Dec 4, 2011 at 2:21 PM, erik quanstrom <quanstro@quanstro.net>wrote:

> > cpu% ndb/dnsdebug
> > > @10.0.0.1
> > > foobar
> > 8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local ip
> > <delay>
>
> sure looks like your the dns packet is being dropped.
> you might want to check your routing.  can you ping 10.0.0.1
> from your linux host (with the interfaces dns is allowed to talk on).
> make sure you see those icmp packets on your plan 9 system
> before proceeding.
>
> - erik
>
>

[-- Attachment #2: Type: text/html, Size: 1960 bytes --]

Re: [9fans] wildcard dns cname

[erik quanstrom]

where is your soa record?

- erik

Re: [9fans] wildcard dns cname

[slash]

[-- Attachment #1: Type: text/plain, Size: 132 bytes --]

>
> where is your soa record?


/lib/ndb/local:

dom=local soa=
refresh=3600 ttl=3600
ns=server.local
mb=email@abcxyz.com

[-- Attachment #2: Type: text/html, Size: 599 bytes --]

Re: [9fans] wildcard dns cname

[slash]

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

ndb/dnsquery also fails for wildcard names but works for real ones:

cpu% ndb/dnsquery
> foooo
!dns: resource does not exist; negrcode 0
> bar
!dns: resource does not exist; negrcode 0
> server
server.local ip 10.0.0.1
> other
other.local ip 10.0.0.2

Why do dnsquery and dnsdebug give different results?

[-- Attachment #2: Type: text/html, Size: 610 bytes --]

Re: [9fans] wildcard dns cname

[slash]

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

>
>
> ndb/dnsquery also fails for wildcard names but works for real ones:
>
> cpu% ndb/dnsquery
> > foooo
> !dns: resource does not exist; negrcode 0
> > bar
> !dns: resource does not exist; negrcode 0
> > server
> server.local ip 10.0.0.1
> > other
> other.local ip 10.0.0.2
>
> Why do dnsquery and dnsdebug give different results?
>
>
For reference here is what dnsdebug gives me:

cpu% ndb/dnsdebug
> fooooo any
----------------------------
answer fooooo.local                        1 hr            came server.local
----------------------------
> bar any
----------------------------
answer bar.local                           1 hr            cname
server.local
----------------------------
> server any
----------------------------
answer server.local                         1 hr            ip   10.0.0.1
answer server.local                         1 hr            cname
server.local
----------------------------
> other any
----------------------------
answer other.local                       1 hr            ip   10.0.0.2
answer other.local                       1 hr            cname server.local
----------------------------

[-- Attachment #2: Type: text/html, Size: 2302 bytes --]

[9fans] wildcard dns cname

[slash]

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

I have the following wildcard entry in my /lib/ndb/local:

cname=server.local
        dom=*.local

Essentially I want every name to resolve back to my server.

Now, ndb/dnsdebug is able to resolve any host just fine:

cpu% ndb/dnsdebug
> foobar
----------------------------
answer server.local                         1 hr            ip   10.0.0.1
----------------------------

But the lookup fails when issued on a unix box:

$ nslookup foobar.local
Server: 10.0.0.1
Address: 10.0.0.1#53

<5 seconds delay>
*** Can't find foobar.local: No answer

Specifying the server in ndb/dnsdebug shows the following:

cpu% ndb/dnsdebug
> @10.0.0.1
> foobar
8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local ip
<delay>
8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local ip
<delay>
8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local cname
<delay>
8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local cname
<delay>
8300.2: sending to 10.0.0.1/10.0.0.1 server.local ip
<delay>
8300.2: sending to 10.0.0.1/10.0.0.1 server.local ip
<delay>
----------------------------
answer server.local                         1 hr            ip   10.0.0.1
----------------------------

How do I fix this so that these dns lookups work without delays on all
machines on my network?

The dns server is started as "ndb/dns -sr" in cpurc.

[-- Attachment #2: Type: text/html, Size: 2841 bytes --]