Host name not resolved using zone

  • Thread starter Thread starter Daniel Tan
  • Start date Start date
D

Daniel Tan

What are the reasons if one of the hosts name not resolved using zone
? if using cached , then it will be ok. I've created a zone for my
domain name in local dns server but it can't be resolved only, when i
delete the zone then it will be solved. Pls advise.

Regards
Daniel
 
In
Daniel Tan said:
What are the reasons if one of the hosts name not
resolved using zone ? if using cached , then it will be
ok. I've created a zone for my domain name in local dns
server but it can't be resolved only, when i delete the
zone then it will be solved. Pls advise.
Click to expand...

You have to create a blank host record. (leave the name field blank)
 
Why is that ? will it create a host name by itself ? Previuosly
usually i will put a host name and it works but until yesterday it
won't.

Regards
Daniel
 
In
Daniel Tan said:
Why is that ? will it create a host name by itself ?
Previuosly
usually i will put a host name and it works but until
yesterday it
won't.
Click to expand...

It will sort of get a name, in the text file its name will be "@" in the DNS
console it will be named "(same as parent folder)"
 
Is it by defaulf cannot put a name ? What if i want to name it something ?

Rgds
Daniel
 
In
Daniel Tan said:
Is it by defaulf cannot put a name ? What if i want to
name it something ?
Click to expand...

If you want the domain name to resolve as just example.com, you have to
leave the name field blank. If you want to name it something the domain name
won't resolve.
 
In
Daniel Tan said:
What if i need it to resolve mail.example.com ?

Rgds
Daniel
Click to expand...

Then you create a 'mail' A record under the example.com zone.

But your original question is on how to resolve 'example.com'. As Kevin
said, that's a blank A record.

Ace
 
In
Daniel Tan said:
What if i need it to resolve mail.example.com ?
Click to expand...
Name the zone mail.example.com with the blank record. You could also name
the zone example.com with a record named mail in the zone, but then the zone
would catch all queries in example.com and you'd have to create those
records, too. It's easier just to name the zone for the record you need it
to resolve to unless you have several hosts to name in the domain.
 
Kevin, what you mean is i can create multiple zones for each host to
resolve or either create an A record named mail or other records under
example.com zone ? Does creating too many zones can slow down dns
server ?

Regards
Daniel
 
In
Daniel Tan said:
Kevin, what you mean is i can create multiple zones for
each host to
resolve or either create an A record named mail or other
records under
example.com zone ?
Click to expand...

You have to make the decision based on how many records need to resolve to
local addresses and how many are in the public domain. If only one or two
need to resolve to local addresses, I'd create them as zones. If however,
all the sites are hosted locally, you might create the zone name for the
domain and create records for mail, www, ftp, etc.
Does creating too many zones can slow
down dns
server ?
Click to expand...

No, if it did there are a lot of DNS servers in trouble with thousands of
zones. You have to set up the machine based on how many hits it is going to
get and the amount of data it needs to transfer on each hit, just like any
other server.
DNS doesn't put much load on a server per hit, as long as the query is
answered from its own zones, if it has to go find the answer it slows DNS
down considerably.
 
So does dns caching put much loads on the server ? Currently it have
to resolve 2 remote hosts under same domain, mail.kobaytech.com and
prpo.kobaytech.com , and i create a zone and under it i create the 2
host records. Is this ok ?

Rgds
Daniel
 
In
Daniel Tan said:
So does dns caching put much loads on the server ?
Click to expand...


A DNS server can answer from its cache as easily as it can from the zones,
once it is cached, but when TTL runs out on the cached record it has to go
resolve it again.
Currently it have
to resolve 2 remote hosts under same domain,
mail.kobaytech.com and
prpo.kobaytech.com , and i create a zone and under it i
create the 2
host records. Is this ok ?
Click to expand...

If the zone is kobaytech.com with just the two records in it, (mail and
prpo) then that is the only two names it can resolve in that domain name. It
won't resolve any other name in that domain name unless you delegate the
name or add the host records for it.
If these are the only two host you need to resolve in the domain you should
probably create zones for the FQDN of the hosts, mail.kobaytech.com and
prpo.kobaytech.com.
 
In
Daniel Tan said:
So does dns caching put much loads on the server ? Currently it have
to resolve 2 remote hosts under same domain, mail.kobaytech.com and
prpo.kobaytech.com , and i create a zone and under it i create the 2
host records. Is this ok ?

Rgds
Daniel
Click to expand...

To answer about load on the server, just having two zones is really just a
drop of water in the lake. I've heard of servers hosting 1000's of zones and
they work perfectly, no problem. So if you were to use a server just as a
caching server, the load will be so small, it would barely be measureable.

:-)

Ace
 
So what you suggest is that i need to create 2 zones for each host ,
mail.kobaytech.com and prpo.kobaytech.com ? If i create zone for this
domain , does the caching still works ?

Rgds
Daniel
 
In
Daniel Tan said:
So what you suggest is that i need to create 2 zones for
each host ,
mail.kobaytech.com and prpo.kobaytech.com ? If i create
zone for this
domain , does the caching still works ?
Click to expand...

If you create the zone for the domain, the only addresses you will be able
to resolve are for the ones that you create in the zone. If you create the
two zones DNS will be able to resolve those two and any other in the domain
that are hosted else where.
 
Back
Top