Errors in domain
Errors in the customer domain ( when they are primary ) can be split down into ;

	Mail records incorrect ( due to addressing or misunderstanding of the MX structure ),
	Glue ( A ( address )) records being incorrect ( pointing at the wrong machine ),
	Missing full stops in the left column ( as a typo, or not knowing they should be there ).

The following tips should help ;

	The format of mail records is :- domain.com. IN MX 10 mail.domain.com. Followed by a record for the mail machine :- mail IN A 1.2.3.4
	Machines should have one name and one address. If multiple names are required use the CNAME function.
	If a fully qualified name is used then a full stop at the end is required.

These are simple solutions for further information please see the DNS and BIND book.

Missing information
The main problem that we face is with information on the request form either missing, or being incorrect. ( This does not count the number of forms that we get with the ip 1.1.1.1 and domain test !).

The only solution to these problems is to go back to the SE or customer and ask for the missing info.
The most basic requests should include;

	Domain name.
	Primary and secondary name server.
	IP addresses of machines in domain.
	Mail host for the domain.

Please ensure that the requests include all information required. If in doubt ask.

Primary server down
Another problem that we frequently see is requests for to be secondary when the primary is down, or unreachable.

Normally we will put the request on hold for a couple of days, and check morning and night to see of the primary comes up. If it does not come up within this time period we will write back asking when the primary is due to be up.

If a request is being submitted for a service where the primary is not yet up, then please include information in the comments section detailing when the primary server is expected to be on the Internet.

Serial numbers incorrect
Changes are made on the primary server but are not reflected on the secondary server.

This is normally because the serial number is not incremented correctly, or the named has not been stopped and restarted.

Whilst the serial can be any number, we suggest that the date is included in it. E.G. 1996062101 The year is in four figures ( to avoid problems with the year 2000 ) with the month, and day, followed by a two digit for number of updates that day. Not only is this easy to read, at a glance you can tell when they last updated, but it is very obvious if the named has not been restarted.

Version of software incorrect
The software that runs the DNS is known as BIND ( Berkeley Internet Name Domain software ). The latest version is BIND 4.9.4-P1

There are known problems with previous versions. One of the common problems is that the secondary server is not updated correctly by the primary name server.

Obtain and compile the latest version of BIND from; The internet software consortium

Invalid request
Invalid request due to lack of understanding. I could write a book on some of the problems that we have had !

This came down to the customer wanting to do something that was not possible. In the end we had to write to them multiple times to advise them on what they should do, and how they should do it.

Again education is required. Please see the DNS and BIND book.

Reverse domain not setup
Reverse domain not setup, has happened a few times, as an oversite, or lack of education.

If you wish to own the whole class C then you have to set up the in-addr.arpa reverse delegation.

The SE's should be getting their technical people to check the requests before they are sent off.

Incorrect zone delegation
Incorrect zone delegation. Secondary address set-up in primary name server incorrectly.

This is due to the customer changing service providers, or mistakes when typing in the new address.
Please remember that the IBM name server should be entered as :- ns.uk.ibm.net. and not by IP address.

Please ensure that the address is entered correctly, and if the secondary is not owned by you, put it in by name and not by IP address.

Example of a Primary domain

; name server data file for xxxxx.com
;*************************************
;*    Start of Authority Records     *
;*************************************
;
@        IN  SOA  ns.uk.ibm.net.  dnsadmin.ns.uk.ibm.net. (
        1996073102; Serial number for this data (yyyymmdd##)
          14400    ; Refresh value for secondary name servers (2 hours)
          3600     ; Retry value for secondary name servers   (1 hour)
          604800   ; Expire value for secondary name servers  (7 days)
          86400 )  ; Minimum TTL value   (1 day)
;
; Define Name Servers
;
                IN    NS    ns.uk.ibm.net.
                IN    NS    ns.de.ibm.net.
;
; Define Hosts in this domain
;
;
xxxxx.com.      IN      MX      10 mail.xxxxx.com.
*               IN      MX      10 mail.xxxxx.com.

xxxxx.com.      IN      MX      10 e-mail.com.		; For IMX customers
*               IN      MX      10 e-mail.com.		; For IMX customers

mail            IN      A       123.456.78.9
www             IN      A       123.456.78.10
anotherweb	IN	CNAME	www.xxxxxx.com.