>
>
> ndb/dnsquery also fails for wildcard names but works for real ones:
>
> cpu% ndb/dnsquery
> > f
> !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
ndb/dnsquery also fails for wildcard names but works for real ones:
cpu% ndb/dnsquery
> f
!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 res
>
> where is your soa record?
/lib/ndb/local:
dom=local soa=
refresh=3600 ttl=3600
ns=server.local
mb=em...@abcxyz.com
where is your soa record?
- erik
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 confi
> cpu% ndb/dnsdebug
> > @10.0.0.1
> > foobar
> 8300.2: sending to 10.0.0.1/10.0.0.1 foobar.local ip
>
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
