Member Avatar for riahc3

Hello

Im trying to make a internal site (Called test.dev) but I cant get it to be viewed internally. I made a A record on the DNS server point "test.dev" to my IP which would be for example 192.168.1.45 but I try to access it on a client PC and it does not resolve. What am I doing wrong?

Thank you!

Edited by ~s.o.s~ because: Moved to proper forum
  • 3 Contributors
  • 3 Replies
  • 182 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by riahc3

Dani AI

Generated

A short, practical addendum based on this thread: good that fixed the immediate problem by adding an A record. For anyone reading this later, the important long‑term gotcha is name choice. The suffix “.dev” is a real gTLD (delegated to Google) and has been included in browser HSTS/preload policies, so modern browsers will force HTTPS for any *.dev name — plain HTTP can be blocked or immediately upgraded and will fail without a valid certificate. (iana.org)
IANA .dev delegation | Google: Broadening HSTS | HSTS preload info

Prefer using names reserved for testing or a subdomain of a domain the organization actually controls. RFCs reserve names such as .test, .example, .invalid and provide guidance about special‑use names; by contrast .local is designated for multicast DNS (mDNS) and can behave very differently on many clients. These standards explain why some “internal” names stop working or conflict with system name resolution. (rfc-editor.org)
RFC 6761 (special‑use names) | RFC 6762 (.local / mDNS)

Operational recommendations that weren’t covered earlier in the replies: adopt split‑horizon (split‑brain) DNS if internal names must differ from public records, and plan certificate management up front — preloaded HSTS means a valid TLS certificate is required for the name, so either use an internal CA trusted by clients or use real, publicly issued certs for names the org controls. Test from representative client platforms (they differ in how they treat .local, single‑label names, and HSTS). (learn.microsoft.com)
Windows Server: DNS policy / split‑brain guidance | HSTS preload requirements

Quick checklist

  • Pick a safe namespace (RFC reserved or a controlled subdomain).
  • Decide split‑horizon vs public records and implement DNS views accordingly.
  • Plan TLS: internal CA or public certs that match the chosen name.
  • Validate from real client devices and browsers; verify no HSTS/certificate errors.

Recommended Answers

All 3 Replies

Member Avatar for jwenting

1) wrong forum
2) impossible to answer without knowing a lot about your network and especially its security settings that you don't want known outside your organisation.

Member Avatar for JorgeM

First determine whether or not you can resolve the host name from a workstation on the LAN. Check your workstation's IP configuration. Is it configured to point to the internal DNS server that is hosting the test.dev zone? If so, from a command prompt type NSLOOKUP. Hit enter. Then type test.dev, and hit enter. Does it resolve to 192.168.1.45? IF not, you need to resolve the name resolution issue.

If it does, but your site does not come up in the browser, its time to shift the focus to the web server (192.168.1.45). Check the web server app your are using, make sure the configuration is correct. If you have more than one website, you either need to assign each web its own IP or port, or use host headers.

If you only have one web site, then check the web site configuration. If you are coding in asp.net or PHP, or any other server side scripting language, before you try to access those types of pages, just set up a test page called default.htm. Can you access this page. If not, still a web server config problem. If you can then move on to trying to resolve your server side scripting config.

At this time, you need to check all of this out and report back if you have any issues. As jwenting mentioned, this is the wrong category of forum. You will get a lot more help if you post your question in the correct category.

If a moderator comes across this thread, he/she can move it for you.

Member Avatar for riahc3

I apoligize as I did not see the network section.

Basically I was able to solve it: Made a A record on the DNS server pointing to the site/IP and done.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.