IN A 127.0.0.1 sirius IN A 192.168.6.1 rigel IN A 192.168.6.112 antares IN A 192.168.6.90 polaris IN A 192.168.6.101 procyon IN A 192.168.6.79 tauceti IN A 188.8.131.52 altair.com. Like other files, you can give it a name other than the name used in this manual. IN SOA com sysop.com ( 1997071401 ; serial number (YYYYMMDD##) 10800 ; refresh every 3 hours 10800 ; retry every 3 hours 604800 ; expire after a week 86400 ) ; TTL of 1 day ; Name Servers 0.0.127. The Defines a named IP address match list used for access control.
Sounds like windows practices (don't care about others, everyone uses our stuff).
OS was installed two weeks ago and updated from karmic repositories.
Meaning the system's resolver will look in /etc/hosts (file) first and if it can't found will ask the configured name server(s) in the same file (bind is a DNS server). No need to reboot it will look in the /etc/each time to know how to resolve names.
Usually the dhcp client will override the content of /etc/resolv.conf, one some systems (most? ) you can create /etc/tail, its content will be appended to /etc/after the override.
Caution – The IP addresses and network numbers used in examples and code samples in this manual are for illustration purposes only. Some statements can contain a contain a block of statements.
Do not use them as shown because they might have been assigned to an actual network or host. Again, each statement in the block is terminated with a semicolon.
So long as you are internally consistent, you can name the zone data files anything you want.
This flexibility can lead to some confusion when working at different sites or referring to different DNS manuals and books.
The easiest project is setting up BIND to do nothing but cache DNS information locally.