[Dnsmasq-discuss] setting up dynamic DNS?

Jan 'RedBully' Seiffert redbully at cc.fh-luh.de
Tue Sep 11 01:31:49 BST 2007


Adam Hardy wrote:
[snip]
> Yes you did say that previously but I was unsure about the requirement
> of the slashes front and back, so I left it unchanged.
> 
> So I changed the dnsmasq.conf again in this way and now the logging
> gives me the following:
> 
> isengard dnsmasq[8120]: reading /etc/resolv.conf
> isengard dnsmasq[8120]: using nameserver 194.74.65.69#53
> isengard dnsmasq[8120]: ignoring nameserver 127.0.0.1 - local interface
> isengard dnsmasq[8120]: using local addresses only for domain
> localdomain.net
> isengard dnsmasq[8120]: query[AAAA] pop.1und1.com from 192.168.0.234
> isengard dnsmasq[8120]: forwarded pop.1und1.com to 194.74.65.69
> isengard dnsmasq[8120]: reply pop.1und1.com is <NODATA>-IPv6

client 192.168.0.234 asks for IPv6 1und1.com
dnsmasq asks upstream
Upstream answer "no ipv6"

> isengard dnsmasq[8120]: query[AAAA] pop.1und1.com.localdomain.net from
> 192.168.0.234
> isengard dnsmasq[8120]: config pop.1und1.com.localdomain.net is
> <NXDOMAIN>-IPv6

client asks for IPv6 1und1.com.localdomain.net
dnsmasq sees from it's config - no

> isengard dnsmasq[8120]: query[A] pop.1und1.com from 192.168.0.234
> isengard dnsmasq[8120]: forwarded pop.1und1.com to 194.74.65.69
> isengard dnsmasq[8120]: reply pop.1und1.com is 212.227.15.177
> isengard dnsmasq[8120]: reply pop.1und1.com is 212.227.15.161
> 

finally the client asks the right questions ;)

> On the eighth line: query[AAAA] pop.1und1.com.localdomain.net ....
> 
> Is this normal - or another misconfiguration?

I wouldn't call it normal, but it's no misconfiguration *AFAIK*.

> Why would dnsmasq think it might have the localdomain.net suffix?

No, the client, or its system resolver libraries.
Since it is an IPv6 enabled client, it tries IPv6 first.
The answer is negativ, so it tries what its /etc/resolv.conf says:
"search localdomain.net"

On the other hand this way the client makes from "gondor" ->
"gondor.localdomain.net".

Maybe you can change the order the client tries IPv6 & IPv4.
OTOH, ISPs should see more IPv6 queries, so we may finally get IPv6 ;)

I would leave it this way, dnsmasq caching abilities and the fact that
these queries are made on a local link with almost no latency makes this
a "don't worry".

> I can imagine it may be dnsmasq
> trying out the name with the local domain appended - just in case it may
> have been an actual simple local hostname without the localdomain.net
> suffix.
> 
Hmmm, that comes into play with the expand-hosts option


> Thank you very much for the help by the way - everyone included.
> 
> Regards
> Adam
> 
> 
Grettings
	Jan

-- 
"...by all means, do not use a hammer."
(from an IBM documentation ca. 1920)



More information about the Dnsmasq-discuss mailing list