can find host name
phn at icke-reklam.ipsec.nu
phn at icke-reklam.ipsec.nu
Sun Feb 10 08:57:35 UTC 2002
Alaa Alamood <aaa at netman.dk> wrote:
> Thanks Again for your responedding
> phn at icke-reklam.ipsec.nu wrote:
>>Alaa Alamood <aaa at netman.dk> wrote:
>>
>>>thanks for answer my
>>>
>>
>>>what do you mean by server / domain, in your quastion.
>>>
>>
>>You did not tell us the _real_ name of the domain and the address of
>>the server , thus we cannot make our own measurements.
>>
> my domain name is: netman.dk
> and the ip is: 193.88.72.6
One of the servers, dkuug.dk (195.215.30.66) is Lame ( not configured as
slave )
You also use rediculasly short TTL's which may cause caches to
loose information early. These days with notify makes short "general" TTL
unneeded.
See RIPE-recommendations for "suitable TTL"
>>Your observations, if i remember right, was that when you ask
>>your nameserver it will answer correct.
>>
> that's right
>> But when you ask a
>>
> when I ask another client that have my master server as a domain name
> server, the following is an example
> of resolv.conf file in one of my clients.
> /etc/resolv.conf
> domain netman.dk
> nameserver 193.88.72.6
> it would not found the hostname that I register in my DNS server
> "193.88.72.6".
"I ask another client" ?? You mean you try in this client or do you mean
that you direct the question to this client ? ( if there is no nameserver
running on this client it _will_ be refused)
Oh, nslookup is dead. Just bury it somwhere where noone will use it.
Use proper tools, like dig host doc dnswalk zonecheck dns-expert etc.
Example with dig shows :
(question is "who does reverse for 193.88.72 " :
> dig 72.88.193.in-addr.arpa ns
; <<>> DiG 8.3 <<>> 72.88.193.in-addr.arpa ns
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;; 72.88.193.in-addr.arpa, type = NS, class = IN
;; ANSWER SECTION:
72.88.193.in-addr.arpa. 23h48m IN NS dkuug.dk.
72.88.193.in-addr.arpa. 23h48m IN NS teapot.netman.dk.
72.88.193.in-addr.arpa. 23h48m IN NS tinderbox.netman.dk.
72.88.193.in-addr.arpa. 23h48m IN NS ns.dknet.dk.
;; ADDITIONAL SECTION:
ns.dknet.dk. 23h47m50s IN A 193.88.44.42
dkuug.dk. 23h47m40s IN A 195.215.30.66
Again, dkuug.dk answers Lame ( not authorative ) :
> dig 72.88.193.in-addr.arpa ns @dkuug.dk.
; <<>> DiG 8.3 <<>> 72.88.193.in-addr.arpa ns @dkuug.dk.
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4
;; QUERY SECTION:
;; 72.88.193.in-addr.arpa, type = NS, class = IN
Which suggest that you either fix dkuug or remove from
delegation records.
> Alaa
>>
>>random nameserver "out there" your recent additions ar'nt there.
>>
>>One way this might happen is of let's say dk. nameservers delegates
>>this zone to other nameservers then yours.
>>
>>Again, it's only a guess.
>>
>>Peter h
>>
>>>I'm going to try to describe the problem in more details
>>>I have master domain server, that have the following named.conf
>>>options {
>>> directory "/etc/namedb/";
>>> query-source address * port 53;
>>>};
>>>zone "." {
>>> type hint;
>>> file "named.ca";
>>>};
>>>zone "0.0.127.in-addr.arpa" {
>>> type master;
>>> file "named.local";
>>>};
>>>zone "domain.dk" {
>>> type master;
>>> file "db.domain.dk";
>>> allow-update {
>>> key netmanDnsKey;
>>> };
>>>};
>>>zone "0.16.172.in-addr.arpa" {
>>> type master;
>>> file "db.172.16.0";
>>> allow-update {
>>> key netmanDnsKey;
>>> };
>>>};
>>>
>>
>>>when I try to make nslookup to a client register in my master domain
>>>server as the following:
>>>
>>
>>>192.168.1.1> nslookup prince.domain.com
>>>Server: 192.168.1.1
>>>Address: 192.168.1.1#53
>>>
>>
>>>Non-authoritative answer:
>>>Name: prince.domain.com
>>>Address: 172.16.0.16
>>>
>>
>>>but
>>>when Im try from another machine
>>>Client> nslookup prince.domain.com
>>>Server: dnsmasterserver.domain.com
>>>Address: 192.168.1.1
>>>
>>
>>>*** dnsmasterserver.domain.com can't find prince: Non-existent host/domain
>>>
>>
>>>please tall me if you need more information?
>>>
>>
>>>regards
>>>
>>
>>>
>>>
>>
>>>phn at icke-reklam.ipsec.nu wrote:
>>>
>>
>>>>Alaa Alamood <aaa at netman.dk> wrote:
>>>>
>>>>
>>>>>phn at icke-reklam.ipsec.nu wrote:
>>>>>
>>>>>>Alaa Alamood <aaa at netman.dk> wrote:
>>>>>>
>>>>>>>Hi
>>>>>>>
>>>>>>>When I try to add host name to the DNS databaser, I can see the host
>>>>>>>name just on the DNS server but not on the others machines. does any one
>>>>>>>have idea what going on
>>>>>>>
>>>>>>>I'm running named version 8.2.2-P5-plus-CA-2000-20-plus-CA-2001-02
>>>>>>>
>>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>
>>>>>orginally come from compaq on tru64unix version 5.1a
>>>>>
>>>>>>Seems to be a candidate to update. nothing named like this have
>>>>>>come out from the original mfg. 8.2.2 however is known to be
>>>>>>malfunctioning.
>>>>>>
>>>>>>What hostname/domain are you talking about ?
>>>>>>
>>>>>the machine that I register on DNS server, I can see it when I make
>>>>>nslookup on the same DNS server, but I can not see it when I make
>>>>>nslookup on the other machine but the server
>>>>>
>>>>Well, you still have not told us what domain / server it is about.
>>>>
>>>>As you describe it it sound like a bad delegation from the parent.
>>>>
>>>>>regards
>>>>>Alaa
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>regards
>>>>>>>Alaa
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>
--
Peter Håkanson
IPSec Sverige (At the Riverside of Gothenburg, home of Volvo)
Sorry about my e-mail address, but i'm trying to keep spam out.
Remove "icke-reklam" and it works.
More information about the bind-users
mailing list