Standard query AAAA turnbui.com.turnbui.com and gets a no such name returnred. Followed by
Standard query AAAA turnbui.com

All other name resolution appears OK.
Can anyone shed some light on where I migt have slipped up please?

I've also noticed the odd
Standard query AAAA images.linuxquestions.org.turnbui.com
as well ?

followed by the normal
Standard query AAAA images.linuxquestions.org

Thanks,

sounds like you may have forgotten a dot (.) somewhere

turnbui.com possibly needs to be turnbui.com.
i fought for a few hours when configuring my first dns using bind and it drove me crazy; it turned out i didnt have a period where it should be...

hope this helps.

Thanks for replying, would it show up in following DIG output?

[root@turnbui ian]# dig turnbui.com axfr

; <<>> DiG 9.2.3 <<>> turnbui.com axfr
;; global options: printcmd
turnbui.com. 259200 IN SOA turnbui.com. root.turnbui.com. 2005090223 28800 7200 2419200 86400
turnbui.com. 86400 IN NS turnbui.com.
turnbui.com. 86400 IN A 192.168.1.7
turnbui.com. 86400 IN MX 10 turnbui.com.
turnbui.com. 86400 IN TXT "dns" "Wizard"
dinsdale.turnbui.com. 200 IN A 192.168.1.10
dnsmaster.turnbui.com. 86400 IN CNAME ian.turnbui.com.
ian.turnbui.com. 1600 IN A 192.168.3.1
ian-test.turnbui.com. 900 IN A 192.168.4.127
ians-wins.turnbui.com. 2400 IN A 192.168.3.1
iant-21.turnbui.com. 1200 IN A 192.168.4.126
iant-21.turnbui.com. 1200 IN TXT "310abf7fdd30ddd7624a76adc762972a71"
iant12.turnbui.com. 500 IN A 192.168.3.254
iant21.turnbui.com. 100 IN A 192.168.1.13
localhost.turnbui.com. 86400 IN A 127.0.0.1
mail.turnbui.com. 86400 IN A 192.168.1.7
Nick.turnbui.com. 300 IN A 192.168.1.12
router.turnbui.com. 86400 IN A 192.168.1.1
tony.turnbui.com. 1200 IN A 192.168.1.11
www.turnbui.com. 86400 IN CNAME ian.turnbui.com.
turnbui.dyndns.dk. 86400 IN CNAME ian.turnbui.com.
hywell.homeip.net. 86400 IN CNAME ian.turnbui.com.
ian21.homeip.net. 86400 IN CNAME ian.turnbui.com.
tony2.homeip.net. 86400 IN CNAME ian.turnbui.com.
turnbui.com. 259200 IN SOA turnbui.com. root.turnbui.com. 2005090223 28800 7200 2419200 86400
;; Query time: 7 msec
;; SERVER: 192.168.3.1#53(192.168.3.1)
;; WHEN: Sat Sep 3 19:53:51 2005
;; XFR size: 25 records

[root@turnbui ian]#

If so I can't spot it?

Cheers

It looks like it is appending turnbui.com to all of your queries.

Check your /etc/resolv.conf file for something like this:

search turnbui.com

If you have a line like that, your DNS setting you have gotten from your DHCP server are telling your system to check turnbui.com for each hostname before seeing them as their own domain.

MrKnisely

I was told I should have search turnbui.com in my resolv.conf. Is this not true?

Also last night at 11:56pm I started getting server failures on DNS queries. I noticed that the Win-XP box was approx 4 miutes faster so I reset it, rebooted and all seemed OK.
I also noticed on checking output from a DNS-HOWTO that I had an extra line in the output from my
dig turnbui.com axfr
command namely turnbui.com. 86400 IN A 192.168.1.7
and thinking I had an error used nsupdate to delete it?
I then went to bed and now when I try to use nsupdate to update delete/add it complains that it can't find Server turnbui.com!!? Since I never had a line like this in my /named/zone/ files and I can't use nsupdate to add it back I'm lost.

Can someone help with this and the resolv.conf question please?

Thanks

Is turnbui.com your domain?

What the "search" does is sticks the domain on any hostname you try to resolve. For example, you could ping www and it will then look for www.turnbui.com first. It is just an easy way of not having to type out a fully qualified domain name when many of your queries will be for that domain.

I use this internally, I have a kniselyhouse.local doamin on my DNS server. That way when I want to ssh into my boxes internally, I can just "ssh www" or "ssh mail." It's just a convenience thing.

Regarding your DNS setup: It looks like you should have that A record for turnbui.com. Right now, the DNS server is not able to resolve itself.

MrKnisely

Thanks for the reply.

Yes turnbui.com is my local domain. So I'm OK with the resolv.conf - ta.

Any ideas on how to get that turnbui.com 86400 A 192.168.1.7
line back into nsupdate? If I try to add it it gives me thge Server or Name not known message !?

Any ideas woulkd be great, thanks

CAn you tell me if in your opinion my DIG output shown earlier looks OK?

This would be a BIG help, please?

Thanks,

I don't understand why you have the .net and .dk domains in your zone file. I don't see how those queries will ever get resolved since your name server is not authoritative for that zone.

Its the only way I've found to point DynDns.org at the correct Apache VHOST from outside on the Web.
But it's not that side I'm worried about. I still have work to do on that side. Getting it working properly on the inside would be a great help.

it's the turnbui.,com.turnbui.com that concerns me. All the other DNS stuff works OK. This includes the reverse lookup etc. Just every so often I find this turnbui.,com.turnbui.com query in the ethereal trace.

Thanks for any help.

Looks like some host on the network has its resolver lib configured to append turnbui.,com.turnbui.com when it creates a query. I would check that host and fix the problem.

BTW: AAAA records are IPv6 queries and the output from your AXFR looks OK to me.
The record in question is simply an address record pointing to your domain name.

I have only used nsupdate with DHCP/DDNS configurations, not adding/deleting records manually. If you are willing to stop named for a few minutes, you can add the record back into the zone file the good ole fashion way. i.e. vi

I had a typo, the comma in the turnbui.com.turnbui.com - sorry if it misled you - silly me.
If I may presume upon you for another wuery?
When a host gets booted and is served an IP it appears BIND/DHCP put a A TXT type record into what dig output shows. When a host on the 192.168.1.0/24 subnet lease expires/retries I appear to be losing this A TXT record and thus lose resolution to that host. It never comes back until I delete that hosts A record and it erboots?!?!?
I realize this should not happen!

To delve a little deeper I'm using my Linux to DHCP on the 912.168.3.0/24 and 192.168.4.0/24 subnet BUT the router is set to give my Linux box a STATIC IP on the 192.168.1.0/24 subnet along with the 3 other XP machines on that subnet.
Is what I'm attempting here illegal?
Naturally I have to tell BIND/DHCP to listen on the NIC on 192.168.1.0/24 otherwise I'd have no chance of detecting when those XP's boot and track them in my Linux DNS.

Did that make much sense.

Again any help / direction would be magic.