|
Bulk Changes Search Pattern
|
NameSurfer 7.6.4.1 |
|||||||||||||||||||||||||||||||||
To search for particular records, or to modify or to remove resource record contents, you need to specify the resource records' types and contents. Leaving the contents field empty means that all the resource records of the specified type are matching. In the resource record contents, patterns are not used. For deletion or for simple searching, you can specify resource record type 'ANY', in which case record contents do not affect the search.
If you want to update the contents of the resource records, you should specify the new value in the "Replace with new RR value" field. This field has no function for record deletion and searching.
If you want to add a new resource record (even if some already existed), you should specify the new value in the "Replace with new RR value" field and click the "Add new RR" button.
An individual SOA field can be changed by clicking the "Change SOA" link located at the NameSurfer's main menu (when the function is available). The SOA record as a whole can then be updated by clicking the "Update" button. The "Change TTL" link located in the NameSurfer main navigation (when the function is available) works in a similar way.
To change TTL values of records, you can use the "Change TTL" tool. After inserting the selection criteria, you will be presented with a list of RRs whose TTL will be changed. Due to rrset definition given in RFC2181 the tool does not allow changing TTLs of individual RRs if a node has several RRs of the same type in it - instead, you can choose to update the TTLs on all RRs of that type on the node.
By clicking one of the submit buttons "Update", "Remove" or "Add new RR", you will be directed to the next page where you can see the search results for the specified patterns. At this point you can still cancel or commit the update.
If your browser supports JavaScript, a result counter will be shown at the bottom of the search page, displaying the number of results your current search would yield. However, if you are going to use the "Add new RR" function, this number does not accurately portray the actual number of individual result nodes that will be shown on the next page because the individual search results are not shown as-is in that case..
The available resource records and their input syntaxes are listed in the following table. More information on a specific record is available via the link in the record's name.
| Resource Record | Purpose | Input Syntax | ||
| A (IPv4 address record) | IPv4 Host address | Ipv4 address, e.g. 192.168.10.10 | ||
| A6 (IPv6 address with aggregation and renumbering support record) | IPv6 Host address | IPv6 address in the form prefix_len suffix prefix_name, e.g. 28 0:0001:CA00:: C.ISP.NET. | ||
| AAAA (IPv6 address record) | IPv6 Host address | Any of the IPv6 formats defined in RFC1884, for example, 1080:0:0:0:8:800:200C:417A | ||
| AFSDB (AFS database record) | Location of AFS database server(s) | <subtype> (16 bit integer) <hostname> (a domain name of a host that has a server for the cell named by the owner name of the RR) | ||
| ALSO_NOTIFY (Also Notify record) | Used for defining a set of name servers for a zone which for some reason should be notified if the zone is changed. Available for nodes only. |
Server host name | ||
| CNAME (Canonical Name record) | A domain-name which specifies the canonical or primary name for the owner. The owner name is an alias. | Domain name | ||
| DHCID (DHCP Identifier record) | Used in conjunction with the FQDN option to DHCP. | SHA-256 hash of host identification data from the DHCP server, presented as a BASE64 -encoded string | ||
| DLV (DNSSEC Lookaside Validation record) | Used for publishing DNSSEC trust anchors outside of the DNS delegation chain. | Key identifier, security algorithm identifier, hash algorithm identifier and a digest value (hexadecimal string) | ||
| DNAME (Delegation Name record) | Creates an alias for a name and all its subnames. Available for nodes only. |
FQDN (Fully Qualified Domain Name) | ||
| DS (Delegation Signer record) | Used for identifying the DNSSEC signing key of a delegated zone. Available for nodes only. |
<key identifier> <security algorithm identifier> <hash algorithm identifier> <digest value> (hexadecimal string) | ||
| HINFO (Host Information record) | Used for identifying the CPU type and operating system of a host. | Text string(s) | ||
| HIP (Host Identity Protocol record) | A method for separating the end-point identifier and locator roles of IP addresses. | <HIT length> <PK algorithm> <PK length> <HIT> <public key> <rendezvous servers> | ||
| HTML (HTML record) | Used for site-specific customization, such as embedding hypertext links or icons in the zone listing | Syntactically correct HTML, suitable for embedding in a HTML table cell | ||
| HTXT (Hidden Text record) | Used for storing confidential information. | Text string | ||
| ISDN (ISDN address record) | Representation of ISDN addresses | <ISDN-address> <sa> (subaddress, optional). | ||
| LOC (Location Record) | Used for attaching geographical location to domain names. | A single-line text representation as specified in RFC1876, for example LOC 42 20 32 N 71 05 19 W 10m 1000m | ||
| MX (Mail Exchange record) | Used for defining where an e-mail addressed to a given domain name gets delivered to. | Mail server host name(s) | ||
| NAPTR (Naming Authority Pointer record) | Allows regular expression based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc. | Standard rules defined in RFC-1035 | ||
| NS (Name Server record) | Used for defining a set of authoritative name servers for a zone. | Name server host name(s) | ||
| NSAP (Network Service Access Point record) | Used for specifying a piece of equipment connected to an Asynchronous Transfer Mode (ATM) network. | <length> (identifies the number of octets in the <NSAP-address>) <NSAP-address> (enumerates the actual octet values assigned by the assigning authority) | ||
| PTR (Pointer record) | Used in the IN-ADDR.ARPA domain to define reverse mappings. Available for nodes only. |
FQDN (Fully Qualified Domain Name) | ||
| REMSEC (Remote Secondary record) | Used for defining the remote secondaries which are set up to be configured automatically. Available for nodes only. |
Remote secondary server host name | ||
| RP (Responsible Person record) | Information on the responsible person(s). | Mail address and domain name, additional TXT records are allowed. | ||
| RT (Route Through record) | Provides a route-through binding for hosts that do not have their own direct wide area network addresses. | <preference> (16 bit integer with smaller numbers indicating more preferred routes) <intermediate-host> (domain name of a host which will serve as an intermediate in reaching the host) | ||
| SOA (Start Of Authority record) | Used for containing various administrative information which applies to the zone as a whole. Available for nodes only. |
Master NS: full domain name Admin e-mail: e-mail address Serial #: integer Refresh: integer Retry: integer Expire: integer Minimum TTL: integer |
||
| SPF (Sender Policy Framework record) | Specified as part of the SPF protocol as an alternative to of storing SPF data in TXT records. | Uses the same format as the earlier TXT record. | ||
| SRV (Service Locator record) | Used for newer protocols instead of creating protocol-specific records such as MX. | _Service._Proto Priority Weight Port Target | ||
| SSHFP (SSH Public Key Fingerprint record) | A resource record used for publishing SSH public host key fingerprints in the DNS System. | Algorithm, fingerprint type and fingerprint | ||
| TXT (Text record) | Used for holding descriptive text | Text string | ||
| WKS (Well Known Services record) | Used for listing the services provided by a host. | IP Address, IP protocol type, a list of port numbers for the service(s). | ||
| X25 (X.25 address record) | Representation of X.25 addresses | Public Switched Data Network address (PSDN-address) | ||