Re: dns records
Well there are a few more... 'TXT' for text records, for ipv6 A records... there are probably more, check the RFC's... For a nice RFC site check http://zvon.org/tmRFC/RFC_share/Output/index.html DNS rfc: http://www.zvon.org/tmRFC/RFC1035/Output/chapter3.html
Re: dns records
Well there are a few more... 'TXT' for text records, for ipv6 A records... there are probably more, check the RFC's... I know that there are a lot more but those are the one's we're actually using currently.
Re: dns records
On Sun, 2003-04-06 at 20:03, Markus Welsch wrote: > i have a few questions regarding dns records for using in a mysql db.the > current layout looks like this: [snip] > typeA > CNAME > MX > NS > PTR > SOA Well there are a few more... 'TXT' for text records, for ipv6 A records... there are probably more, check the RFC's... -- Mark Janssen -- maniac(at)maniac.nl -- GnuPG Key Id: 357D2178 Unix / Linux, Open-Source and Internet Consultant @ SyConOS IT Maniac.nl Unix-God.Net|Org MarkJanssen.org|nl SyConOS.com|nl
dns records
hi all, i have a few questions regarding dns records for using in a mysql db.the current layout looks like this: class CH HS IN data name preference ttl typeA CNAME MX NS PTR SOA The class is not really required. Regarding the type, that are all the types currently in use. If you do a lookup of e. g. www.debian.org at http://www.network-tools.com/nslook/Default.asp?domain=www.debian.org&type=255&server=66.46.181.133&class=255&port=53&advanced=true you will see more clear what each field exactly means. I thought of using enum for the type, varchar for data and name, smallint (2) for preference, varchar(8) for ttl since it could be alpha-numeric. How large can a preference be (MX records) ? What about the length of data and name ? Greetings, Markus
