Datacenter IP Addressing and DNS Management

datacenterdomain-name-systemip

We are setting up a small Datacenter, about 300 amps power and max 50 racks,

I have studied networking mostly Microsoft and Windows based systems , but I do not understand the IP addressing, DNS management and configuration works in a Datacenter, and unfortunately I have to setup everything by myself but,we will have some staff to do some job.

My questions

Datacenter IP Addressing

Suppose we have got a block of 200 IP addresses from our ISP,

How can I manage these block of IP addresses, is there any software out there to simplify this I heard that using DHCP server in a datacenter is not recommended, otherwise what would you say about MS DHCL serverconsidering we need to have backup server(s) in case of failure
How can I assign a block of IPs to a specific rack, I know with different software and management its different but Im asking how it is done normally
IP addresses are exposed to the whole network, what if a customer tries to use an IP address and is not assigned to their server or rack , how can I prevent this or how can I track the IP usage

DNS Management

Im goin to setup at least two servers for our DNS servers, I know nothing about Datacenter DNS system, but I have configured DNS server in normal networks and also for webservers, Now I wanna know.

What exactly needs to be done for a DNS in a datacenter that is not done for normal networks.
How can I configure PTR records
why cant I configure PTR records on my webserver side DNS server and it should be done on datacenter DNS server , I mean what is the difference in DC DNS servers that allow us to to so
, I know the question is very silly and simple but Im confused

Is there any software outthere to allow doing the whole thing, I mean automatically add records to the DNS and also managin IP addresses !?

Thanks in advance

Best Answer

It's not the answer you're looking for per-se but I'd reccomened getting a contracter in or hiring someone who knows what they are doing rather than asking on a FaQ site.

Also, are you sure you can make it? What's to separate you from the hundreds and thousands of hosting companies?

Related Solutions

How are DNS PTR records managed

or are they stoerd in separate zones?

Separate zones, one per old C network (last byte in the octet).

What stops me from adding a PTR record saying that resolves to say gmail.com?

Nothing. But as this is not used exceptt for nice pings or some email validity checks, you achieved nothing. people will still go to gmail when they type in gmail.com. All people now see is gmail.com in a traceroute, nothing else.

The one real use for this is smtp - the HELO string given in SMTP should match the PTR record name given. Basically the server must say it is who the ptr record says it is. Note that it can still accept emails for other domains.

How to check name servers for reverse DNS

Puting information into whois depends on owner of block address - it's not obligatory. If owner put it, you can ask for example as

whois 1.254.150.in-addr.arpa

If you want to ask for authoritative nameserver, better ask ns-es for it desceding for every octet, for example:

undefine@undefine-ThinkPad-T430s:~$ host -t NS 150.in-addr.arpa
150.in-addr.arpa name server apnic.authdns.ripe.net.
150.in-addr.arpa name server ns1.apnic.net.
150.in-addr.arpa name server tinnie.arin.net.
150.in-addr.arpa name server ns3.apnic.net.
150.in-addr.arpa name server ns4.apnic.net.
150.in-addr.arpa name server ns2.lacnic.net.
150.in-addr.arpa name server apnic1.dnsnode.net.
undefine@undefine-ThinkPad-T430s:~$ host -t NS 254.150.in-addr.arpa
254.150.in-addr.arpa name server ns.ripe.net.
254.150.in-addr.arpa name server rose.man.poznan.pl.
254.150.in-addr.arpa name server sunflower.man.poznan.pl.
undefine@undefine-ThinkPad-T430s:~$ host -t NS 1.254.150.in-addr.arpa
1.254.150.in-addr.arpa name server orion.put.poznan.pl.
1.254.150.in-addr.arpa name server sol.put.poznan.pl.
1.254.150.in-addr.arpa name server sunflower.man.poznan.pl.

Another option is using dnstracetool. for example:

undefine@undefine-ThinkPad-T430s:~$ dnstracer -4 -s A.ROOT-SERVERS.NET 140.141.180.213.in-addr.arpa
Tracing to 140.141.180.213.in-addr.arpa[a] via A.ROOT-SERVERS.NET, maximum of 3 retries
A.ROOT-SERVERS.NET (198.41.0.4) 
 |\___ a.in-addr-servers.arpa [in-addr.arpa] (2001:0500:0013:0000:0000:0000:0000:0073) Not queried
 |\___ a.in-addr-servers.arpa [in-addr.arpa] (199.212.0.73) 
 |     |\___ tinnie.arin.net [213.in-addr.arpa] (199.212.0.53) 
 |     |     |\___ dns3.onet.pl [141.180.213.in-addr.arpa] (213.180.147.200) 
 |     |     |\___ dns1.onet.pl [141.180.213.in-addr.arpa] (213.180.128.242) 
 |     |      \___ dns2.onet.pl [141.180.213.in-addr.arpa] (213.180.137.160) 
 |     |\___ tinnie.arin.net [213.in-addr.arpa] (2001:0500:0013:0000:0000:0000:c7d4:0035) Not queried
 |     |\___ pri.authdns.ripe.net [213.in-addr.arpa] (193.0.9.5)

You can also use dig to trace dnsservers, for example:

undefine@undefine-ThinkPad-T430s:~$ dig +trace 141.180.213.in-addr.arpa

; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> +trace 141.180.213.in-addr.arpa
;; global options: +cmd
.           116349  IN  NS  h.root-servers.net.
.           116349  IN  NS  i.root-servers.net.
.           116349  IN  NS  c.root-servers.net.
.           116349  IN  NS  d.root-servers.net.
.           116349  IN  NS  f.root-servers.net.
.           116349  IN  NS  m.root-servers.net.
.           116349  IN  NS  e.root-servers.net.
.           116349  IN  NS  a.root-servers.net.
.           116349  IN  NS  j.root-servers.net.
.           116349  IN  NS  k.root-servers.net.
.           116349  IN  NS  b.root-servers.net.
.           116349  IN  NS  l.root-servers.net.
.           116349  IN  NS  g.root-servers.net.
.           518057  IN  RRSIG   NS 8 0 518400 20160414050000 20160404040000 60615 . pRQcZjdxUQk8wXYugudP6hxIoftDZ40Ofg8jL3I12Qi4ohu5zmABUngi ecglIDv9CNfP8WmzvRV8YfojLR2jLLPuaeBHLBr6bCJEcoI3HMzZXefY 0vEQ+MGGx1I6LbQPqmfwUnaxFOTV3Sf2THqHvFoTOcGtDln/7S692q+K S/Y=
;; Received 913 bytes from 172.31.31.31#53(172.31.31.31) in 39 ms

in-addr.arpa.       172800  IN  NS  a.in-addr-servers.arpa.
in-addr.arpa.       172800  IN  NS  b.in-addr-servers.arpa.
in-addr.arpa.       172800  IN  NS  c.in-addr-servers.arpa.
in-addr.arpa.       172800  IN  NS  d.in-addr-servers.arpa.
in-addr.arpa.       172800  IN  NS  e.in-addr-servers.arpa.
in-addr.arpa.       172800  IN  NS  f.in-addr-servers.arpa.
in-addr.arpa.       86400   IN  DS  47054 8 2 5CAFCCEC201D1933B4C9F6A9C8F51E51F3B39979058AC21B8DF1B1F2 81CBC6F2
in-addr.arpa.       86400   IN  DS  53696 8 2 13E5501C56B20394DA921B51412D48B7089C5EB6957A7C58553C4D4D 424F04DF
in-addr.arpa.       86400   IN  DS  63982 8 2 AAF4FB5D213EF25AE44679032EBE3514C487D7ABD99D7F5FEC3383D0 30733C73
in-addr.arpa.       86400   IN  RRSIG   DS 8 2 86400 20160413180000 20160403170000 38746 arpa. VX53RKpx6w0zTPAHbWssxukkwqqEHf52SC0fCqMA05wuf7Ye1M8DdI/F fD8pZypFAcQ5I/y+c4V6o+g8M21G6kJSIk3ZPfBWpGOWyUYtmLNXRwzE cEj6Gr40LwTjNfT0oh/e3x5MEpp+oST2wA0iM2y605LZlyNFCTQ/e8mF kJA=
;; Received 737 bytes from 192.58.128.30#53(j.root-servers.net) in 21 ms

213.in-addr.arpa.   86400   IN  NS  ns3.nic.fr.
213.in-addr.arpa.   86400   IN  NS  pri.authdns.ripe.net.
213.in-addr.arpa.   86400   IN  NS  sec1.apnic.net.
213.in-addr.arpa.   86400   IN  NS  sec3.apnic.net.
213.in-addr.arpa.   86400   IN  NS  sns-pb.isc.org.
213.in-addr.arpa.   86400   IN  NS  tinnie.arin.net.
213.in-addr.arpa.   86400   IN  DS  38870 8 2 FB9D9B5A72B7A1F6B084018119354A23AAAF434A056B8BEE0A77DD12 F77750E7
213.in-addr.arpa.   86400   IN  RRSIG   DS 8 3 86400 20160416101758 20160325215946 10720 in-addr.arpa. II/3Q2FWRcz08KTGrvzTgNQz/GmOHYVwy4JTooLJA3NQof6Ybnpr5KIm VJbO/iPexiKLG1Y6RhRW4pOacImMjfrYdkuSA11yaqDJ//JZkX1IUEiZ RFhSL34dPGnpRWrmJR6q2+6yzqjDAcpfZBG2XURxEpXg4D1Wl+8L3qer B30ILeY=
;; Received 432 bytes from 199.253.183.183#53(b.in-addr-servers.arpa) in 35 ms

141.180.213.in-addr.arpa. 172800 IN NS  dns2.onet.pl.
141.180.213.in-addr.arpa. 172800 IN NS  dns3.onet.pl.
141.180.213.in-addr.arpa. 172800 IN NS  dns1.onet.pl.
141.180.213.in-addr.arpa. 3600  IN  NSEC    142.180.213.in-addr.arpa. NS RRSIG NSEC
141.180.213.in-addr.arpa. 3600  IN  RRSIG   NSEC 8 5 3600 20160503170152 20160403160152 2878 213.in-addr.arpa. FpW883TIz9SxqyEarBr5hTx4wLTPwk2Ey2Ps5BQqrWtocCPHq/BDEW7u aktTAH6ik7NzcYarleElzO0GyG5XyR4DkHy+j3sHzmqWtwDta9WSwQ/f ajm9187SYo2HaPu0bQ3Y9OKvA4iSgBGxheFfkdQE4Yuor2Mm9Hjy/L4r JdA=
;; Received 339 bytes from 192.134.0.49#53(ns3.nic.fr) in 56 ms

141.180.213.in-addr.arpa. 7200  IN  SOA dns1.onet.pl. dns.onet.pl. 2015112402 300 7200 2419200 86400
;; Received 105 bytes from 213.180.128.242#53(dns1.onet.pl) in 15 ms

Best Answer

Related Solutions

How are DNS PTR records managed

How to check name servers for reverse DNS

Related Topic