Who manages the DNS for my company domain?

DNS records are managed by the party hosting the DNS — most often the domain registrar or hosting provider. It is important that the company maintains access to DNS management itself and does not rely exclusively on an external provider.

What are SPF, DKIM, and DMARC?

These are DNS records that tell the email recipient which servers are allowed to send email on behalf of your domain (SPF), how to verify the digital signature (DKIM), and what should happen if verification fails (DMARC). Together, they significantly reduce the possibility of email spoofing.

Why doesn't a DNS record change take effect immediately?

DNS records have a TTL value — how long intermediaries should store them. Until the TTL expires, different recipients may see different values. For planned changes, we set the TTL to a low value before the intervention.

Why shouldn't internal DNS be an ISP's DNS (e.g., 1.1.1.1)?

ISP DNS servers do not know the names of your company's internal servers and domain resources. This means that AD login, access to shared folders, and internal applications either break or operate unstably.

Networks

DNS(DNS)

Angleški izraz: Domain Name System

Kratka definicija

A system that converts human-readable names (e.g., vitalit.si) into IP addresses that computers understand.

Kaj pomeni DNS?

DNS (Domain Name System) is a distributed naming system that translates a domain name (for example vitalit.si) into the IP address of the server to which the device actually connects. Without DNS, we would have to remember numbers instead of names.

In a business environment, DNS operates at two levels: public DNS (for the company domain and its records visible to the internet) and internal DNS (for the names of internal servers, applications, and domain resources).

Various types of records are important in DNS: A (name → IPv4 address), AAAA (name → IPv6), MX (where to send email for this domain), TXT (arbitrary records, including SPF, DKIM, and DMARC for email security), and CNAME (aliases).

Zakaj je to pomembno za podjetja?

DNS is the quiet backbone of all business services. If an email does not reach its destination, the cause is often an incorrect MX, SPF, or DMARC record. If a website 'does not work' from the office, the cause is often internal DNS rather than the website itself.

Properly configured DNS also means better email security: SPF, DKIM, and DMARC records tell recipients which servers are allowed to send email on behalf of your domain. Without them, your domain is more exposed to spoofing and phishing.

Kje se to pojavi v praksi?

A typical example of business use: public DNS for the company domain (vitalit.si) handles website records, MX records for email in Microsoft 365, and SPF/DKIM/DMARC records for anti-spoofing protection.

Internal DNS (usually on Active Directory domain controllers) handles the names of internal servers and computers. Properly configured internal DNS ensures that users do not have to deal with IP addresses.

Najpogostejše težave ali napake

The most common problem: changes to public DNS that take longer than they should due to high TTL values — in practice, an MX record change may only take full effect after several hours or even a day.

Another common problem: missing or incorrectly configured SPF, DKIM, and DMARC records. The result is that company emails either end up in the spam folder or can be easily forged by someone else.

The third error: using ISP DNS servers instead of domain controllers for internal DNS. The results are problems logging into the AD environment, slow opening of shared folders, and nonsensical error messages.

Kako pri tem pomaga VitalIT

At VitalIT, we help companies organize both public and internal DNS. For existing environments, we first check the status of DNS records, SPF/DKIM/DMARC settings, and the health of internal DNS servers.

In practice, we prepare a change plan (being mindful of TTLs), set up SPF/DKIM/DMARC for email protection, fix internal DNS on domain controllers, and prepare documentation on who manages the DNS and how. We adapt the solutions to the actual environment and the agreement with the client.

Omrežja in požarne pregrade Sistemska integracija

Sorodni izrazi

VLAN

A logically separated network on the same physical equipment that allows different groups of devices to function separately as if they were on different cables.

Firewall

A device or software that monitors and filters network traffic between different networks, protecting the internal environment from unauthorized access.

VPN

An encrypted connection between a user and the business network that allows employees to work securely with internal resources from anywhere.

Povezane storitve

Omrežja in požarne pregrade Sistemska integracija

Pogosta vprašanja

Who manages the DNS for my company domain?: DNS records are managed by the party hosting the DNS — most often the domain registrar or hosting provider. It is important that the company maintains access to DNS management itself and does not rely exclusively on an external provider.
What are SPF, DKIM, and DMARC?: These are DNS records that tell the email recipient which servers are allowed to send email on behalf of your domain (SPF), how to verify the digital signature (DKIM), and what should happen if verification fails (DMARC). Together, they significantly reduce the possibility of email spoofing.
Why doesn't a DNS record change take effect immediately?: DNS records have a TTL value — how long intermediaries should store them. Until the TTL expires, different recipients may see different values. For planned changes, we set the TTL to a low value before the intervention.
Why shouldn't internal DNS be an ISP's DNS (e.g., 1.1.1.1)?: ISP DNS servers do not know the names of your company's internal servers and domain resources. This means that AD login, access to shared folders, and internal applications either break or operate unstably.