DNS

DNS support lets labs resolve names instead of hard-coding every address. netverdict includes a resolver and wire model for the supported query paths.

Support level

Area	Level	Notes
DNS resolver	Behaviour model	Resolves configured records for lab traffic.
UDP/53 wire path	Behaviour model	DNS messages can travel through the modelled network.
A records	Supported	IPv4 name resolution.
AAAA records	Partial	IPv6 support where configured.
Recursive Internet DNS	Not modelled	Lab-local deterministic resolution only.

Standards coverage

Standard	Coverage	Notes
RFC 1034 / RFC 1035	Partial	Query/response concepts and basic record handling.

Feature matrix

Feature	Status	Notes
DNS server config	Supported	Configures lab resolver state.
Client resolver	Supported	Uses configured DNS server.
A record lookup	Supported	Name to IPv4.
Negative response	Behaviour model	Missing names fail deterministically.
CNAME/MX/TXT	Not modelled	Out of scope today.

Vendor command matrix

Command	IOS-style	Junos-style	VyOS-style	Notes
ip name-server 192.0.2.53	Supported	Partial	Partial	Resolver target.
ip host app 192.0.2.10	Supported	n/a	Partial	Static host record.
show hosts	Supported	Partial	Partial	Host/resolver view.

Behaviour notes

DNS is deterministic and topology-local. It is meant to make service labs and management workflows readable, not to emulate the public DNS hierarchy.

Examples

Canonical example

configure terminal
ip name-server 192.0.2.53
ip host app 192.0.2.10
end
ping app
show hosts

Vendor styles

IOS-style

ip name-server 192.0.2.53
ip host app 192.0.2.10

Junos-style

set system name-server 192.0.2.53
set system static-host-mapping app inet 192.0.2.10

VyOS-style

set system name-server 192.0.2.53
set system static-host-mapping host-name app inet 192.0.2.10

Known limits

Recursive resolution, caching TTL races, DNSSEC, CNAME chains, SRV/MX/TXT records, and EDNS details are not implemented.